@manta-templates/mcp

MCP server for Manta Templates — exposes component discovery, content system knowledge, and composition guidance to AI agents.

What is this?

@manta-templates/mcp is a Model Context Protocol (MCP) server that gives AI agents structured knowledge of the Manta Templates component library. Agents can discover available components, query content type schemas, and get composition guidance for building pages — without reading source files directly. It is designed for use with AI coding assistants such as Claude Code and Cursor.

Quick Start

Install

# Run without installing
npx -y @manta-templates/mcp

# Or install globally
npm install -g @manta-templates/mcp

Configure for Claude Code

claude mcp add manta-templates -- npx -y @manta-templates/mcp

Or add to .mcp.json in your project root:

{
  "mcpServers": {
    "manta-templates": {
      "command": "npx",
      "args": ["-y", "@manta-templates/mcp"]
    }
  }
}

Configure for Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "manta-templates": {
      "command": "npx",
      "args": ["-y", "@manta-templates/mcp"]
    }
  }
}

Available Tools

Component Discovery

| Tool | Description | |------|-------------| | component_list | Lists components with optional category filter (cards, layouts, navigation, forms, utilities, theme). Returns name, category, and short description. | | component_detail | Returns full metadata for a named component: props, variants, injection points, and usage examples. | | component_search | Searches components by keyword across names, descriptions, props, and categories. |

Content System

| Tool | Description | |------|-------------| | content_types | Lists all available content types (project, article, quote, video, about, technology) with their frontmatter schemas. | | content_schema | Returns the full schema for a specific content type, including field definitions and example frontmatter. | | content_structure | Describes content directory conventions, file naming, slug derivation, and discovery mechanism. | | content_provider | Explains provider setup (ViteContentProvider for React), hook usage (useContent, useContentCollection), and caching. |

Composition & Configuration

| Tool | Description | |------|-------------| | page_patterns | Returns composition patterns for common page types (homepage, blog index, blog post, about, examples, legal). | | theme_options | Returns available themes (light/dark), accent palettes (8 options), ThemeProvider setup, and CSS variable overview. | | site_config | Describes the site.config.ts pattern: site metadata, contacts, presets, and footer variant selection. | | layout_guide | Explains layout composition: BentoLayout span control, Container sizing, GridContainer, GridLayout, and CardCarousel setup. | | header_footer | Describes EnhancedHeader configuration (nav styles, variants, mobile breakpoints) and footer variants. |

Server

| Tool | Description | |------|-------------| | server_version | Returns the current MCP server version. |

Troubleshooting

"Failed to connect" on first launch

The first npx -y @manta-templates/mcp invocation downloads the package and resolves its dependencies, which can take several seconds. If your MCP client's startup handshake times out before the server is ready, the connection is reported as failed even though the server itself is healthy.

Two ways to fix it:

Warm the npx cache once. Run the command manually so the package is cached locally:

npx -y @manta-templates/mcp

Press Ctrl-C once it prints Server started. Subsequent launches will start in well under a second because the package is cached under ~/.npm/_npx/.

Increase the MCP startup timeout. Claude Code honors MCP_TIMEOUT (in milliseconds). Set it in your shell profile to give cold launches more headroom:

export MCP_TIMEOUT=30000

Or install globally to bypass npx entirely (fastest, no registry lookups):

npm install -g @manta-templates/mcp
claude mcp add manta-templates -- manta-templates-mcp