An agent writing frontend code has to know the backend's API. It has three options. It can read the backend source and work out from scratch what the service already publishes. It can ask you, which promotes you to API documentation. Or it can swallow the entire OpenAPI document in order to use one route out of it.
Then it does the same thing again tomorrow, against a stale swagger.json
you exported last week.
docs-mcpserver
takes the spec straight from the running service, caches it, and serves it one operation at a time.
{
"cacheDir": "./cache",
"libraries": [
{
"name": "orders-api",
"description": "Order handling service",
"sources": [
{
"type": "url",
"origin": "https://localhost:5001/openapi/v1.json",
"kind": "schema",
"name": "orders"
}
]
}
]
}
npm install -g docs-mcpserver
claude mcp add docs -- docs-mcpserver --config /path/to/dev-docs.json
That is the whole setup.
The agent lists the definitions in orders
, picks the one it needs, and fetches that. For an OpenAPI document the path operations are exposed as definitions named GET /orders/{id}
, so it can also search by keyword.
A few hundred tokens for the operation it is writing against, instead of the entire document. That keeps working as the service grows, which a pasted spec does not.
Every call is answered from the cached spec, never from the network. The fetch happens on startup and then in the background while you work, so an endpoint you added 20 seconds ago is already visible.
Start the backend once, shut it down, and keep building the frontend. The agent still has real routes and real payload shapes. If the service is down, or answers with something that is not a spec, the last known-good copy keeps being served.
Code and issues: github.com/jgauffin/dev-docs-mcp. On npm as docs-mcpserver
.