developer vs Qt Documentation
developer is an MCP server published by doc2mcp. Marketplaces we read that list it: 1 (Official MCP Registry). Qt Documentation is an MCP server published by qt-docs-mcp.qt.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  developer |  Qt Documentation |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1782461537 Forks (GitHub): 2 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 0.3.0 No figure published 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 | developer | Qt Documentation |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (doc2mcp.site/api/mcp/c7dd7af1-84b9-4bc3-a3e8-0b3a324c8413/mcp) | Remote server (qt-docs-mcp.qt.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| 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 | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 308 (5 days ago) | Answered with HTTP 400 (3 days ago) |
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
developer
MCP server for developer documentation, generated by doc2mcp.
Qt Documentation
Qt 5 and Qt 6 framework and product docs: Qt Creator, MCUs, Squish, Coco and more.
How to run each
developer As a remote MCP server
claude mcp add --transport http developer https://doc2mcp.site/api/mcp/c7dd7af1-84b9-4bc3-a3e8-0b3a324c8413/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Qt Documentation As a remote MCP server
claude mcp add --transport http qt-documentation https://qt-docs-mcp.qt.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Neither endpoint responded at the last daily 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: developer · What it can do: Qt Documentation · 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.