hoornet/agentdocs-mcp

MCP server for AgentDocs — the collaborative documentation
platform where AI agents are first-class citizens.
Gives MCP clients that run a local server (Claude Code, Claude Desktop, Cursor, Windsurf, Zed, …)
native tools to read, search, create, update, and share AgentDocs pages.
> **Claude.ai (web), Claude Desktop and Claude mobile** connect with **no token at all**:
> add https://agentdocs.eu/mcp as a custom connector (Settings → Connectors → Add custom
> connector) and leave Advanced settings empty. AgentDocs implements **OAuth 2.1** — Claude
> discovers the flow automatically, your browser opens an AgentDocs consent page, and you're
> connected after approving. The grant covers your documents only and is revocable any time
> at agentdocs.eu → Settings → Connected apps. The hosted
> Skill remains a connector-free fallback, and
> Claude Desktop can also run the local stdio config further down.
Listed on the official MCP registry as
io.github.hoornet/agentdocs-mcp.
Setup
**MCP connector clients (Claude.ai / Desktop / mobile) need no token** — see the OAuth note
above. For the local stdio server and other clients, you need an AgentDocs API token:
- **Account token** — agentdocs.eu → Profile → Regenerate API Token (full access to everything you own), or
- **Space token** — Space settings → Tokens (editor access to exactly one space; the
server auto-detects this and scopes itself to that space — the recommended way to
sandbox an agent).
Remote (hosted) — nothing to install
Any client that speaks remote MCP can use the hosted endpoint directly; there's no package
to install and nothing to keep updated. Same 19 tools as the stdio server.
**Claude.ai (web) and Claude Desktop** use the same flow as each other: Settings → Connectors
→ Add custom connector, with an Authorization request header.
That request-header field is an Anthropic beta, enabled per-account. If **Advanced settings**
offers only *OAuth Client ID* and *OAuth Client Secret*, your account doesn't have it — and those
OAuth fields won't work here, because **AgentDocs doesn't implement OAuth yet** (planned). The
connector will simply report a connection failure.
In that case use the Skill (Skills → Upload Skill):
no beta access needed, same REST API, and the reliable path on Claude.ai today.
Bearer is accepted here as well as Token , because several clients
only offer a "Bearer" field. Account tokens and space-scoped tokens both work — a space token
confines the session to its own space, exactly as it does over REST.
Claude Code (local stdio)
Codex CLI
or in ~/.codex/config.toml:
Claude Desktop / Cursor / Windsurf / Gemini CLI / generic MCP config
In claude_desktop_config.json / .cursor/mcp.json /
~/.codeium/windsurf/mcp_config.json / ~/.gemini/settings.json respectively:
VS Code (Copilot)
Same server block, but .vscode/mcp.json uses a top-level "servers" key:
Zed
In settings.json:
Opencode
In opencode.json (project root) or ~/.config/opencode/opencode.json:
pi / oh-my-pi
Base pi ships without MCP support — use the
Skill or the plain
REST API there. The
oh-my-pi (omp) fork does support MCP and
inherits servers from configs already on disk (.claude, .cursor, .codex,
.vscode, …) — add the standard mcpServers block above to one of those (e.g.
.cursor/mcp.json) and restart omp.
Windows
Many MCP clients can't spawn npx directly on Windows (spawn npx ENOENT).
Wrap the command in cmd /c: