network

---

What is this repo?

This is the public face of doc2mcp on GitHub:

Repo	Visibility	Purpose
doc2mcp/doc2mcp-registry (this repo)	Public	MCP Registry manifest, badges, discovery
doc2mcp/doc2mcp	Private	Product code (not open source)

The live product runs at doc2mcp.site. Source code stays private so the platform cannot be copied.

How it works

1. Sign in at doc2mcp.site/login
2. Paste a docs URL (Stripe, LangChain, your own Mintlify site, OpenAPI, GitHub repo…)
3. Get a hosted MCP URL + Bearer token
4. Paste into Cursor / Claude / VS Code mcp.json
5. Every MCP you create is auto-listed on the official MCP Registry as io.github.doc2mcp/<slug>

{
  "mcpServers": {
    "my-docs": {
      "url": "https://doc2mcp.site/api/mcp/{project_id}/mcp",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

CLI

npm install -g doc2mcp
doc2mcp login
doc2mcp https://docs.example.com

MCP Registry

Entry	Namespace
Platform gateway	io.github.doc2mcp/doc2mcp
Your converted docs	io.github.doc2mcp/<slug> (auto-published on each conversion)

• Registry search: https://registry.modelcontextprotocol.io/?search=doc2mcp
• Marketplace: https://doc2mcp.site/marketplace

Gateway manifest (server.json)

This repo publishes the canonical platform record via GitHub OIDC when you push a v* tag:

git tag v1.0.2
git push origin v1.0.2

Workflow: .github/workflows/publish-mcp.yml

Why a separate public repo?

The MCP Registry grants namespace io.github.doc2mcp/* only to workflows running inside the doc2mcp GitHub org. This small public repo holds the OIDC publish manifest — not the product source.

Links

• 🌐 Product: https://doc2mcp.site
• 📦 npm CLI: https://www.npmjs.com/package/doc2mcp
• 📋 MCP Registry: https://registry.modelcontextprotocol.io/?search=doc2mcp
• 🏆 Product Hunt: https://www.producthunt.com/products/doc2mcp
• ✉️ Contact: doc2mcp@gmail.com

License

The server.json manifest in this repo is MIT. The doc2mcp product code is proprietary and not distributed in this repository.