io.github.hoornet/agentdocs-mcp vs io.github.yuque/yuque-mcp
io.github.hoornet/agentdocs-mcp is an MCP server published by hoornet. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.yuque/yuque-mcp is an MCP server published by yuque. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.10.4 Downloads/month (npm): 782 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.4 Downloads/month (npm): 1 266 Downloads/week (npm): 201 Forks (GitHub): 28 Stars (GitHub): 257 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 | io.github.hoornet/agentdocs-mcp | io.github.yuque/yuque-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 257 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 28 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (agentdocs.eu/mcp) | On your machine (yuque-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 3 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hoornet/agentdocs-mcp | github.com/yuque/yuque-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 13 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
io.github.hoornet/agentdocs-mcp
AgentDocs (agentdocs.eu) MCP: read, search, write, comment, share & attach images to Markdown docs.
io.github.yuque/yuque-mcp
MCP server for Yuque — expose your knowledge base to AI assistants.
How to run each
io.github.hoornet/agentdocs-mcp As a remote MCP server
claude mcp add --transport http agentdocs-mcp https://agentdocs.eu/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: AGENTDOCS_TOKEN (secret), Authorization header
io.github.yuque/yuque-mcp As a local MCP server: npm package
claude mcp add --env "YUQUE_GROUP_TOKEN=<YOUR_YUQUE_GROUP_TOKEN>" --env "YUQUE_PERSONAL_TOKEN=<YOUR_YUQUE_PERSONAL_TOKEN>" --env "YUQUE_TOKEN=<YOUR_YUQUE_TOKEN>" --transport stdio yuque-mcp -- npx -y yuque-mcp
Requires: YUQUE_GROUP_TOKEN (secret), YUQUE_PERSONAL_TOKEN (secret), YUQUE_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.hoornet/agentdocs-mcp 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
Only io.github.hoornet/agentdocs-mcp asks for
AGENTDOCS_TOKEN (secret)AGENTDOCS_URL
Only io.github.yuque/yuque-mcp asks for
YUQUE_GROUP_TOKEN (secret)YUQUE_PERSONAL_TOKEN (secret)YUQUE_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.hoornet/agentdocs-mcp · What it can do: io.github.yuque/yuque-mcp · 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.