Live API context

MCP Layer

Give Cursor, Claude Code, and every agent on your team live access to your internal API catalog over MCP. They query the current spec — never a stale doc or a 150k-token paste — in around 300 tokens.

Get started free See the platform →

Pasting vs querying, side by side

Stop pasting OpenAPI specs into Cursor. Stop guessing if they're current.

Two strategies, same task. One feeds the agent a wall of stale YAML and hopes. The other answers the question the agent actually asked — over MCP, the moment it asks.

Strategy A

Pasting OpenAPI specs

~5,200 tokens

paths:
  /orders/{id}/refunds:
    post:
      summary: Issue a refund
      requestBody:
        content:
          application/json:
            schema:
              properties:
                amount:
                  type: integer
                partialRefund:
                  type: boolean
  ...and 4,800 more lines of unrelated endpoints

Pasted at 9am. By lunchtime, the spec changed. The agent doesn't know.

Strategy B

spec0 MCP query

~400 tokens

// get_api_spec("orders-api", "POST /orders/{id}/refunds")
operation: POST /orders/{id}/refunds
summary: Issue a refund
headers:
  Idempotency-Key: string  // required
body:
  amount_minor_units: integer  // required
  partial: boolean
  reason: enum
    - "requested_by_customer"
    - "fraudulent"
    - "duplicate"

Queried at the moment the agent needed it. Always current. Never more than what's asked.

How it connects

Three paths in, one live registry out.

Push a spec from CI, the web UI, or the CLI. spec0 indexes it as operations, components & metadata — governed by your team structure — and serves it to every agent over one MCP endpoint. No per-agent setup, no stale copies.

Three paths in, one live registry out

Indigo flows in as specs are pushed; emerald flows out as agents query. The registry in the middle is the only source of truth — every client reads the same current spec.

The toolbox

What your agents can do over MCP.

The MCP layer exposes your catalog as a focused set of tools. Agents call them like any other function — no scraping, no pasting, no guessing field names.

search_apis

Find the right API

Semantic search across every API in your org — the agent describes the task, not the filename.

get_api_spec

Fetch just what's needed

A bounded slice of any spec — the one operation the agent asked for, not 5,000 lines of YAML.

get_operation

Full operation detail

Params, request body, responses, and auth for a single endpoint — correctly named, every time.

get_api_changelog

Stay current

What changed between versions, so the agent writes against today's contract — not last quarter's.

get_api_owner

Know who owns it

The team behind an API and how to reach them, surfaced inline when the agent needs a human.

list_apis

See the whole catalog

Enumerate exactly the APIs this agent is entitled to — governed by your team structure.

One command

Connect the client you already use.

If your editor speaks MCP, spec0 works. Install once and every agent in that client can query your catalog — no per-project config to copy around.

Cursor
Claude Code
Claude Desktop
Continue.dev
Cline
+ any MCP client

bash

$ spec0 mcp install --client cursor
→ writing MCP server config…
✓ spec0 configured for Cursor
  restart the client and your catalog is live

The platform

Part of the spec0 platform

See the whole platform →