INDIVIDUAL MCP TOOL

get_recipe

Complete, runnable files that combine several Layro components the way they fit together: an AI chat app shell (Sidebar + Conversation History + AI Chat, with a phone drawer), a dashboard app and a billing page.

layropro.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://layropro.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_recipe and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description suggests code or command execution.

Parent server

layropro.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.layro]
url = "https://layropro.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "layro": {
      "type": "http",
      "url": "https://layropro.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: layro
Remote MCP URL: https://layropro.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "layro": {
      "url": "https://layropro.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "layro": {
      "type": "http",
      "url": "https://layropro.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "layro",
  "transport": "streamable-http",
  "url": "https://layropro.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

search_components — Find Layro React + Tailwind components by what they do.
get_component — Everything about one component except its source: when to use it, props, variants, npm dependencies, the files it installs, a typechecked usage example with real props, how it sizes and scrolls (layout), the components it pairs with and the recipes it appears in.
get_component_code — The complete source for one component and every file it imports, ready to save at the paths given.
get_installation — Installation for one or more components: the one-time @layro registry setup for components.json, the shadcn CLI command (always @layro/<slug>, never a bare URL), a ready-to-run agent command with a 15-minute install token when this connection carries a CLI token, the npm packages still missing (pass installed_packages from package.json), the files and where they go, and the theme setup.
list_categories — The categories in the Layro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accessibility and responsive behaviour every component has.
search_templates — Find complete Layro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.
get_template — One template's details and whether the caller may download it.
check_access — Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.