MCP Server

Standalone

Airy MCP now lives in a separate repository. This registry site publishes the data bundle and shadcn registry; the standalone MCP service reads that data and owns transport, caching, tools, and response shape.

Repository Boundary

Airy Registry

This repo owns source registry files, generated theme token JSON, docs, rules, and the shadcn install output at /r. It also keeps /api/mcp as the stable public URL by rewriting it to the standalone MCP service.

Standalone MCP

levco/airy-mcp owns the MCP runtime. It fetches /mcp-data/index.json, caches the bundle, and adapts resolved theme tokens for target clients.

Endpoints

MCP endpointhttps://airy.lev.com/api/mcp

Public Airy MCP endpoint. This rewrites to the standalone airy-mcp service.

Standalone targethttps://airy-mcp.vercel.app/api/mcp

Underlying Streamable HTTP server hosted from the airy-mcp repo.

Health checkhttps://airy-mcp.vercel.app/api/health

Standalone server readiness check.

MCP data indexhttps://airy.lev.com/mcp-data/index.json

Generated data bundle published by this registry repo.

shadcn registryhttps://airy.lev.com/r

Installable Airy registry output for shadcn clients.

Connect

Cursor

Add the remote MCP endpoint to your project's .cursor/mcp.json:

{
  "mcpServers": {
    "airy": {
      "url": "https://airy.lev.com/api/mcp"
    }
  }
}

Claude.ai

Go to Settings, then Connectors, then Add custom connector, and paste:

https://airy.lev.com/api/mcp

Claude Desktop

Add the remote endpoint to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "airy": {
      "url": "https://airy.lev.com/api/mcp"
    }
  }
}

Local MCP Development

Develop the server from levco/airy-mcp. Point local runs at the production Airy data bundle:

AIRY_DATA_URL=https://airy.lev.com/mcp-data/index.json
AIRY_REGISTRY_BASE_URL=https://airy.lev.com/r

Data Bundle

The bundle is generated during registry:build and served from /mcp-data. It is intentionally small so the standalone server can change response shape without changing registry source files.

Included

registry.json
resolved theme token JSON generated from registry/airy-theme/*.css
registry/airy-guidelines/*.md
registry/airy-rules/*.md

Excluded

registry/static/**
old PPTX/static specs
old per-part MCP payload artifacts
the in-repo MCP server implementation

Contract

The durable contract from this repo is the published data: installable registry files, rules, guidelines, and resolved theme token JSON. MCP tool names, payload layout, and client-specific adapters live in the standalone server so they can evolve independently.

Operations

After this registry deploys new /mcp-data, the standalone server refreshes from the published index on its cache schedule. Use the health endpoint to confirm the generated timestamp and cache status. For MCP behavior changes, update levco/airy-mcp; for source token, rule, guideline, or registry data changes, update this repo.

Smoke tests

GET https://airy-mcp.vercel.app/api/health
POST https://airy.lev.com/api/mcp with MCP initialize
POST https://airy.lev.com/api/mcp with tools/call