Cowork writes the doc. You send the link.
Add AgentDoc as an MCP server in Claude Cowork and every doc it writes can be published to a real URL — readable by anyone, no Claude account required. Drop-in MCP config. Private by default.
{
"mcpServers": {
"agentdoc": {
"command": "npx",
"args": ["-y", "@agentdoc/mcp"]
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (create the file if it doesn't exist) and restart Cowork. On first run the MCP server provisions an anonymous account and caches the key at ~/.agentdoc/mcp-key.json — no email, no OAuth. Claim it later when you want a username, custom domain, or shared workspace.
Cowork is great at writing. Sharing is the gap.
Cowork drafts the launch plan, the SOP, the client update, the research note. It writes a clean markdown file in a folder on your Mac. Good work, fast.
Now you need to send it to someone outside Claude. Your client, your cofounder, your contractor. So you copy-paste into Google Docs, attach the.mdfile, or paste the content into a message — and the moment Cowork edits it again, the shared copy is stale. There's no public URL. No version history past the last save. No way for another agent to read it.
AgentDoc gives every doc Cowork writes a real URL. Publish in one ask — the doc lives at /@you/slug with a raw markdown endpoint at /@you/slug.md for other agents. Cowork keeps editing locally; the link stays live.
What Cowork gains.
The MCP server adds four primitives Cowork doesn't have on its own.
A real URL anyone can open
Cowork publishes to /@you/slug — a clean webpage that loads without Claude, without an account, on any device.
Raw .md endpoint for agents
/@you/slug.md serves the underlying markdown so other agents (Claude Code, Cursor, ChatGPT, custom) can read what Cowork wrote.
Version history with attribution
Every edit is named — Cowork, you, a teammate, another agent. See exactly how a doc evolved and revert any version.
Private by default
Every doc starts private. Cowork (or you) explicitly publishes when ready. Unpublish in one click — the URL stops working immediately.
Three steps. No new app.
Add the MCP server to Cowork
Paste the JSON snippet above into claude_desktop_config.json and restart Cowork. Cowork now has 47+ tools for reading, writing, and publishing agentdocs.
Ask Cowork to publish
"Publish the launch plan as q2-launch-plan." Cowork creates the doc, publishes it, and returns the URL. No context switch.
Send the link, keep editing
Drop the URL in iMessage, Slack, email. Ask Cowork to update the doc later — the link stays live, the readers see the latest.
What Cowork can do, once it's installed.
Just ask. The MCP server exposes 47+ tools; you don't need to remember any of them.
- “Publish the launch plan we just drafted as an agentdoc.”
- “Update q2-launch-plan with the channel changes my client requested.”
- “Read the latest version of the SOP and use it as context for the next draft.”
- “Make q2-launch-plan unlisted — I want a link with a secret token, not a public page.”
- “Show me the version history of the client brief and tell me what changed in the last edit.”
- “Invite alex@acme.com as an editor on this doc — they don't need an agentdocs account.”
Frequently asked questions
Do I need an agentdocs account before I install?
Does the person I send the link to need a Claude account?
What if I want the doc to stay private?
Does Cowork count as a paid seat?
Can I edit the doc on agentdocs.com instead of in Cowork?
What does this cost?
One config block. Cowork ships links.
No new app to learn. No account ceremony. Just ask Cowork to publish, and send the URL.
{
"mcpServers": {
"agentdoc": {
"command": "npx",
"args": ["-y", "@agentdoc/mcp"]
}
}
}