doc2mcp vs picomcp docs
doc2mcp is an MCP server published by doc2mcp. Marketplaces we read that list it: 1 (Official MCP Registry). picomcp docs is an MCP server published by picomcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  doc2mcp |  picomcp docs |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1783805784 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | doc2mcp | picomcp docs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (doc2mcp.site/api/mcp/5bfd0790-3cac-4fef-8632-6fb6eb8fa71a/mcp) | On your machine (picomcp-docs) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/doc2mcp/doc2mcp-registry | github.com/picomcp/picomcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-03 |
| Endpoint at the last check (differs) | Answered with HTTP 308 (20 h ago) | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
doc2mcp
MCP server for doc2mcp documentation, generated by doc2mcp.
picomcp docs
Search and read the picomcp docs while your agent writes TypeScript MCP servers.
How to run each
doc2mcp As a remote MCP server
claude mcp add --transport http doc2mcp https://doc2mcp.site/api/mcp/5bfd0790-3cac-4fef-8632-6fb6eb8fa71a/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
picomcp docs As a local MCP server: npm package
claude mcp add --transport stdio picomcp-docs -- npx -y picomcp-docsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only doc2mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: doc2mcp · What it can do: picomcp docs · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.