Docs MCP server
Give your coding agent live access to this documentation — a hosted MCP server with search_docs, list_docs, and get_doc, authenticated with your normal Dystopic API key.
Dystopic hosts an MCP (Model Context Protocol) server that exposes this documentation to AI agents. Connect it to Claude Code, Cursor, Claude Desktop, or Codex and your agent can search and read the docs directly — always the live published version, never a stale snapshot.
Why connect it
An agent with the docs MCP attached can answer "how do I register an agent?"
or "what flags does odyssey ci take?" from the actual reference pages instead
of guessing from training data. It is most useful when:
- Porting or authoring an agent with a coding assistant. The assistant can pull the exact SDK signatures, YAML shapes, and CLI flags while it writes code.
- Wiring CI. The CI and gate pages change as the product does; the agent reads the current ones.
- Platform agents. Workflow LLM tool-calling fields and Odyssey agents can bind the same three tools, so an agent running on Dystopic can consult the docs mid-run.
Tools
| Tool | What it does |
|---|---|
search_docs(query, limit=10) | Keyword search over the docs index. |
list_docs() | Full table of contents, grouped by section. |
get_doc(path) | Full Markdown for one page — accepts a slug, a /docs/... path, or a URL. |
Connect
The server lives at https://api.pipelines.tech/mcp and authenticates with a
normal Dystopic API key (pk_live_...), sent as either
Authorization: Bearer <key> or X-API-Key: <key>.
Claude Code
claude mcp add --transport http dystopic-docs \
https://api.pipelines.tech/mcp \
--header "Authorization: Bearer pk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Verify with claude mcp get dystopic-docs.
Claude Desktop, Cursor, and other JSON-configured clients
{
"mcpServers": {
"dystopic-docs": {
"type": "http",
"url": "https://api.pipelines.tech/mcp",
"headers": {
"Authorization": "Bearer pk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}The "type": "http" line matters — without it some clients assume a local
stdio command.
Codex
export DYSTOPIC_API_KEY=pk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
codex mcp add dystopic-docs \
--url https://api.pipelines.tech/mcp \
--bearer-token-env-var DYSTOPIC_API_KEYNotes and limits
- Hosted connector UIs are not supported. ChatGPT connectors and Claude's hosted custom-connector flow require OAuth; this server uses static bearer keys, so it works from local MCP clients only.
- Rate limit. Requests are capped per client (HTTP
429with aRetry-Afterheader when exceeded). Docs reads are small and cached, so normal agent use stays well under it. - Prefer plain Markdown? The same content is available without MCP:
GET /llms.txton the docs site is a Markdown index of every page, and each page's raw Markdown is what the "Copy page" button copies.