Doc2 MCP Server

doc2mcp — MCP Registry manifest

This repository is not the doc2mcp product. It is the small, GitHub‑OIDC‑authenticated publishing manifest for the official Model Context Protocol Registry.

Why a separate repo?

The MCP Registry uses GitHub OIDC to claim a namespace. Whichever GitHub org or user runs mcp-publisher publish from a workflow gets exclusive publishing rights to io.github.<that-org>/*.

Since we want the public, brandable namespace io.github.doc2mcp/* (instead of io.github.gautammanak1/*), the publish workflow must run inside the doc2mcp GitHub organization. This repository holds only the publishing manifest and workflow — nothing else.

gautammanak1/doc2mcp   →  product code, Vercel deploy, docs site
doc2mcp/doc2mcp        →  this repo. server.json + publish workflow

What clients should use

To connect to doc2mcp from Cursor, Claude Desktop, VS Code, Windsurf, the OpenAI Agents SDK, etc., point your MCP host at the remote URL in server.json:

{
  "type": "streamable-http",
  "url": "https://doc2mcp.site/api/mcp/{project_id}/mcp",
  "headers": { "Authorization": "Bearer <your project MCP token>" }
}

Get your project_id and Bearer token from doc2mcp.site → Dashboard → your project → Connect tab.

Publishing flow

Pushing a vX.Y.Z tag to main triggers .github/workflows/publish-mcp.yml, which:

1. Updates the version field in server.json to match the tag.
2. Installs the official mcp-publisher CLI.
3. Authenticates via GitHub OIDC (id-token: write).
4. Publishes the manifest to the registry.

To cut a new version:

# from this repo
git tag v1.0.2
git push origin v1.0.2

The workflow validates against the upstream JSON Schema before publish, so a bad description length or missing required field will fail loudly with a clear error.

License

The manifest in this repo is published under the MIT License. The doc2mcp product itself is licensed in its main repository.