LibAry MCP Server

MCP server so AI IDEs (Cursor, Claude Code, etc.) can browse and install LibAry components directly.

Tools

| Tool | Description | |------|-------------| | list_components | List every component in the registry | | get_component | Get metadata + full source for a component | | add_component | Install a component (stdio only) or return files to create (remote HTTP) |

Remote setup (recommended)

Add the hosted MCP URL to your IDE — no local clone or path required:

{
  "mcpServers": {
    "lib-ary": {
      "url": "https://libary.dev/mcp"
    }
  }
}

Use the MCP Setup button in the LibAry sidebar to get the exact config for Cursor, VS Code, Windsurf, or Claude Desktop.

Self-host the HTTP server

npm run mcp:http

The server listens on http://localhost:8787/mcp by default. Set PORT to change it.

When deployed with the site (e.g. Vercel), /mcp is rewritten to the API handler.

Local stdio setup

For full add_component support (writes files to your machine), run over stdio:

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

From the LibAry repo after install:

{
  "mcpServers": {
    "lib-ary": {
      "command": "npm",
      "args": ["run", "mcp", "--workspace", "@lib-ary/mcp"],
      "cwd": "/absolute/path/to/LibAry"
    }
  }
}

Example prompts

• "List all LibAry components"
• "Show me the modal component source"
• "Add shimmer-text to my project"

Install behavior

• Remote HTTP: add_component returns source files and CLI instructions for your agent to apply locally
• Local stdio: writes to src/components/lib-ary/<component>/ by default
• Creates libary.json on first install in the target project
• Skips existing files unless force: true