Skip to main content

@layero

@layero is an MCP plugin for AI IDEs that lets you build a finished landing page right in the Cursor / Claude Code / Codex chat. No editor, no terminal: one install button → an @layero ... conversation → a deployed page.

Unlike the CLI flow, which deploys an existing project, @layero creates a landing page from scratch off a short brief.

What is inside​

  • 5 design systems — minimal, editorial, terminal, warm, bold. Each one is a palette plus typography plus a set of ready components in vanilla HTML and CSS.
  • 6 structures — masterclass, portfolio-dev, portfolio-designer, portfolio-mentor, event, saas. Semantic HTML with no inline styles.
  • Composition — any structure × any design system = a finished landing page. Eleven artefacts yield up to 30 distinct pages.
  • A series of quizzes — the IDE renders native forms (through MCP elicitation); the plugin asks about motivation, vibe and integration, then picks the three closest design candidates itself.
  • Deploying to Layero is part of the flow: once the files are generated the plugin runs npx layero@latest deploy --json through the agent's bash tool.

Quick start​

  1. Open land.layero.app (the install page)
  2. Press Add to Cursor — the IDE opens and offers to install the MCP server
  3. In the IDE chat, write: 
    @layero I want a landing page for a pottery workshop, warm vintage style
  4. Fill in three short forms (taste, tone, where submissions go)
  5. Done — the files are in your workspace and the landing page is deployed

How it works technically​

The plugin is a remote MCP server at https://mcp.layero.ru/mcp, speaking the Streamable HTTP transport.

[ Cursor / Claude Code ]
         │ JSON-RPC over HTTPS
         ▼
[ mcp.layero.ru ]   ← MCP server in Python (FastMCP)
         │
         ├── building:  compose_landing, list_design_systems, list_structures
         ├── shipping:  publish_landing, add_integration
         ├── operating: site_status, diagnose_deploy, check_performance
         ├── setup:     env_vars, connect_domain, check_domain, list_domains
         ├── analytics: connect_analytics, site_analytics
         ├── account:   whoami, my_projects
         └── resources: layero://soul, layero://catalogue

Sixteen tools — and no longer just "build me a landing page". The plugin publishes the result itself (no Node and no terminal on your side), reports the state of a site, diagnoses a failed deploy, connects a domain and analytics, and compares speed before and after. It covers the whole cycle, not only the first step.

SOUL — the plugin's philosophy​

The plugin follows a fixed set of behavioural rules, written down in SOUL.md:

  • Beautiful landings should take zero effort. The user thinks about what; the plugin thinks about everything else.
  • Asking is a tax. Acting is a gift. Every question costs the user attention. If it can be decided without them, decide it.
  • Confidence over options. A confident default beats five choices.
  • Static is a feature. HTML and CSS by default. React plus Vite only when real interactivity is needed. No SSR.

Where to go next​