MCP

Connect agents to the catalogue over Model Context Protocol. The server exposes the same registry as the CLI.

Endpoint

https://compounddesign.vercel.app/mcp

Server card

https://compounddesign.vercel.app/.well-known/mcp/server-card.json

How to connect

HTTP transport, no authentication. In Claude Code, add this to your MCP configuration file:

{
  "mcpServers": {
    "compound-design": {
      "type": "http",
      "url": "https://compounddesign.vercel.app/mcp"
    }
  }
}

Tools

list_topics

The catalogue's topics, with how many skills each holds. Use it before listing: there are hundreds of entries, and picking a topic keeps the agent's context from filling up for nothing.

list_skills

Lists the skills, in pages of 40. Filters by free text and by topic, and takes limit and offset. Each item carries author and licence, not just name and description.

get_skill

Fetches a skill's markdown by name, slug or author/slug. Use name: "start" for the routing skill. When a name exists under more than one author, it returns the options instead of choosing for you.

Why it comes paginated

The whole catalogue in one response came to 157 KB, roughly 40,000 tokens landing in the context of an agent that only wanted to know what exists. Listings come in pages of 40 and say how much was left out, with the offset for the next. Nothing is trimmed in silence.

Limits

No authentication, with a ceiling of 120 calls per minute per address. A normal session makes about a dozen; the ceiling is there to catch an agent stuck in a loop.

Provenance

The 207 hosted ones come back with the text and the attribution. The other 62 come back with the card and the source address: without a declared licence, serving the text would mean redistributing what is not ours.