Install — the one-click way
Open Settings → Connectors → Add custom connector in Cowork (or Claude.ai) and paste:
https://mcp.agentdoc.com
Click Connect. Claude runs the OAuth flow and agentdoc tools show up immediately. No file editing, no shell, no restart, no Node version headaches — works identically on Claude.ai web, Desktop, and Cowork's sandbox.
This is the path we recommend for everyone. Skip to Publish from any conversation below.
Local stdio install (escape hatch)
Use this only if you specifically want the MCP server running locally (air-gapped, custom env, paranoid about network). Requires Node 18+ on your machine.
Technical — paste in your terminal:
npx -y @agentdoc/cli install claude-cowork
The CLI merges an agentdoc entry into ~/Library/Application Support/Claude/claude_desktop_config.json without touching your other MCP servers.
Not technical — paste in Cowork:
Set up AgentDoc for me: https://agentdoc.com/install/claude-cowork.md
Cowork fetches the install markdown, edits its own config file, and tells you what it did. Restart Cowork after install either way — Cowork does not hot-reload MCP servers.
Tip
Already have an AgentDoc API key? Add an env block to the MCP entry: "env": { "AGENTDOC_API_KEY": "ad_sk_xxx" }. Otherwise the MCP provisions an anonymous key on first use at ~/.agentdoc/mcp-key.json.
Manual install (no shell, no chat)
If you'd rather edit the file yourself, paste this into ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"agentdoc": {
"command": "npx",
"args": ["-y", "@agentdoc/mcp"]
}
}
}
Restart Cowork. On first run the MCP server provisions an anonymous API key.
If you see fetch is not defined in the MCP logs
Your npx resolved to a Node <18 install — common with nvm when an older version sits earlier on PATH. Fix:
nvm install 20
nvm alias default 20
Then fully quit Cowork (Cmd-Q, not just close the window) and relaunch.
Publish from any conversation
"Publish the launch plan we just drafted as
q2-launch-plan."
Cowork creates the doc, publishes it, and returns https://agentdoc.com/@you/q2-launch-plan. That link works for anyone — no Claude account on the other end.
Keep editing — the link stays live
"Update
q2-launch-planwith the channel changes my client requested."
Cowork pulls, edits, and pushes the new version. Viewers see the update. Version history records that Cowork made the edit.
One-line capabilities
- Public webpage:
/@you/slug— clean, mobile, dark mode, OG card. - Raw markdown for other agents:
/@you/slug.md. - Private by default:
visibility: PRIVATEuntil you explicitly publish. - Unlisted: secret-token URL, not indexed. Ask Cowork to publish as
UNLISTED. - Invite a human: "Invite alex@acme.com as editor." They don't need an AgentDoc account.
- Version history: every edit attributed (Cowork vs. you vs. a teammate).
- Unpublish: one click, the URL stops working.
Cost
Free for individuals. $12/user/mo for a shared workspace. Cowork never counts as a seat.
Claim the account later
curl -X POST https://api.agentdoc.com/v1/claim \
-H "Content-Type: application/json" \
-d '{"email":"you@acme.com","claim_token":"<token from ~/.agentdoc/mcp-key.json>"}'
Attaches an email, creates a Clerk account, gives you a username and the dashboard at agentdoc.com.
Every other agent
Claude Code, Cursor, Codex, Windsurf, Zed, VS Code, ChatGPT — see agentdoc.com/connect. Each one has its own /install/<slug>.md a non-technical user can paste in chat.