Documentation tooling just got a serious upgrade for terminal natives. Doc2MCP, the CLI tool that transforms documentation sites into Model Context Protocol servers, is now available directly from npm—letting developers skip the web interface entirely and work 100% from their shell.

Getting Started in Seconds

Installation is straightforward: run npm i -g doc2mcp and you're ready to roll. The setup process includes a browser-based authentication flow—no wrestling with API keys or environment variables. When you run doc2mcp login, it prints a short code and authorization link, you approve in your browser, and the CLI is authenticated instantly. If the global install doesn't register on your PATH, the post-install output tells you exactly what to add.

From Documentation URL to MCP Server

The core workflow is beautifully simple: point doc2mcp at any documentation URL with doc2mcp https://docs.example.com, and it handles the rest. The CLI crawls and indexes the site, provisions a hosted MCP endpoint with a token, then prompts you to install directly into your editor of choice—Cursor, VS Code, Claude, or Windsurf. It writes the config files for you. No JSON wrangling required.

Interactive Documentation Chat in Your Terminal

The standout feature is doc2mcp chat, a REPL-style interface that lets you query documentation interactively. Run it against any docs URL and paste a question—you get formatted terminal output with headings, bold text, lists, code blocks, and clean source links rendered properly instead of raw markdown. The tool also supports one-shot queries via doc2mcp chat -m "your question here" for quick lookups without entering the interactive shell.

Why Hosted MCPs Change the Game

The hosted and token-based architecture solves a real problem: your editor reuses the same MCP instance instead of scraping documentation on every request. This means faster response times and lower infrastructure overhead—both critical when you're iterating quickly or working with large documentation sets across multiple projects.

Key Takeaways

  • doc2mcp login — Browser-based authentication (no API keys)
  • doc2mcp — Convert any docs site into a hosted MCP server
  • doc2mcp chat [url|id] — Interactive REPL for querying documentation
  • doc2mcp list — View your existing MCP projects
  • doc2mcp install — Add an existing MCP to your editors

The Bottom Line

Doc2MCP's terminal-first approach cuts out the middleman entirely—no web UI, no manual config editing, just straight CLI-to-MCP conversion. For developers already living in their terminals, this is the workflow documentation tooling should have had from day one.