Doc2mcp
Wire your doc2mcp-generated project documentation into Claude Code or Cursor so the agent answers from your official docs instead of guessing APIs.
Overview
doc2mcp is an MCP server for the Build phase that serves doc2mcp project documentation to your coding agent over authenticated streamable HTTP.
What is this MCP server?
- Streamable HTTP remote MCP at doc2mcp.site with Bearer token auth from the project Connect tab
- Auto-generated from doc2mcp so docs and MCP tools stay aligned with your published documentation set
- Treats the project MCP token as a secret password—required Authorization header on every request
- Hosted remote—no local Node process to maintain for doc lookup during agent sessions
- Repository source on GitHub under doc2mcp/doc2mcp for the generator and server definition
- Server schema: MCP 2025-12-11 server.schema.json
- 1 streamable-http remote endpoint on doc2mcp.site
- 1 required secret Authorization header (Bearer project MCP token)
What problem does it solve?
Agents invent APIs and miss edge cases when your doc2mcp docs live in a browser tab they cannot search reliably during a coding session.
Who is it for?
Indie builders already using doc2mcp to publish docs who want one MCP endpoint for the doc2mcp project reference inside Claude Code or Cursor.
Skip if: Teams that need write access to repos, runtime observability, or documentation that is not published through doc2mcp.
What do I get? / Deliverables
After you register the remote server with your Bearer token, the agent can pull answers from your doc2mcp documentation set while you build.
- Live remote MCP connection to doc2mcp project documentation from your agent
- Authenticated doc lookup workflow without maintaining a local MCP server binary
- Aligned doc surface—the MCP server is generated from the same doc2mcp documentation pipeline
Recommended MCP Servers
Journey fit
Documentation MCP servers sit on the build shelf because solo builders add them while implementing features and need authoritative reference material in the agent loop. Docs subphase is the canonical home for servers whose primary job is exposing written product and API documentation to coding agents.
How it compares
Remote documentation MCP integration, not a local agent skill or CLI doc scraper.
Common Questions / FAQ
Who is Doc2mcp MCP for?
Solo builders and small teams using Doc2mcp who want coding agents to read the Doc2mcp project documentation through MCP instead of manual copy-paste.
When should I use Doc2mcp MCP?
Use it during build and integration work whenever you need accurate API and product details from your Doc2mcp-hosted docs inside an agent session.
How do I add Doc2mcp MCP to my agent?
Copy the Bearer MCP token from the Doc2mcp project Connect tab, add the streamable-http remote URL to your agent MCP settings, and set Authorization to Bearer plus that token.