The folks behind doc2mcp just dropped a CLI that lets you turn any documentation site into a hosted MCP server without ever leaving your terminal. If you've been watching the MCP ecosystem evolve, you know this is the kind of tooling that makes the whole stack actually usable in production. The web version was already solid—now it's shell-native.

Getting Started

Installation is straightforward: npm i -g doc2mcp. The post-install step prints a PATH fix if needed, or you can just run it via npx as a fallback. Authentication uses a browser-based flow—no fumbling with API keys. Run doc2mcp login, get a short code and link, approve in your browser, and you're authorized. Clean separation between CLI and web auth means no credential headaches.

Converting Docs to MCPs

Point the tool at any documentation URL with doc2mcp . The CLI crawls and indexes the site, then spits out a hosted MCP URL plus token. Here's where it gets interesting: instead of handing you raw JSON config to copy-paste manually, it asks which editor you want to install into—Cursor, VS Code, Claude Desktop, or Windsurf—and writes the configuration for you automatically.

The Chat REPL Is Where It's At

The killer feature is doc2mcp chat. It's a Claude Code-style REPL that lets you query your converted docs directly in the terminal. Paste a URL, it converts on the fly, offers to install into your editors, then drops you into an interactive session. Answers render as formatted output—headings, bold text, lists, and fenced code blocks—instead of dumping raw markdown at you. You can also fire off one-shot questions: doc2mcp chat -m "how do I authenticate?"

Why Hosted MCPs Matter

The hosted-and-token-based approach solves a real problem. Your editor reuses the same MCP instead of re-scraping docs every time—that means faster responses and lower infrastructure overhead. Build once, use everywhere across your team. The doc2mcp list command shows all your projects, and you can install any existing MCP into new editors with doc2mcp install .

Key Takeaways

  • One-line install via npm: npm i -g doc2mcp && doc2mcp login
  • Browser-based auth eliminates API key management entirely
  • Direct editor integration with Cursor, VS Code, Claude Desktop, and Windsurf—no manual config editing
  • Interactive chat REPL for querying docs in your terminal with formatted output
  • Hosted MCPs mean reuse across sessions and lower scraping overhead

The Bottom Line

This is the kind of tool that makes MCP adoption actually happen in real workflows instead of staying in the "interesting demo" phase. Cutting out the config friction and adding a proper chat interface puts docs querying on par with talking to a well-prompted AI assistant—and that's exactly where this ecosystem needs to go.