Zed is fast. AgentDoc is the URL layer.
Wire AgentDoc into Zed as a context server so the assistant can read and publish docs without leaving the editor.
npx -y @agentdoc/cli install zedPrefer manual setup? Paste this into ~/.config/zed/settings.json▾
{
"context_servers": {
"agentdoc": {
"command": {
"path": "npx",
"args": ["-y", "@agentdoc/mcp"]
}
}
}
}Zed reloads the config live — no restart required. The CLI shortcut merges the entry into your settings.json.
What Zed gains.
The MCP server adds primitives Zeddoesn't have on its own.
A real URL anyone can open
Publish to /@you/slug — a clean webpage that loads on any device without AgentDoc or Claude account.
Raw markdown endpoint for agents
/@you/slug.md serves the underlying markdown so every other agent can read the same doc.
Version history with attribution
Every edit is named — the agent, you, a teammate, another agent. See how a doc evolved and revert any version.
Private by default
Docs start private. Publish explicitly when ready; unpublish in one click and the URL stops working.
What Zed can do, once installed.
Just ask — no new tools to memorize.
- “Publish the design doc we wrote this morning as design/auth-flow.”
- “Open the most recent version of the onboarding AgentDoc.”
Frequently asked questions
Do I need an AgentDoc account before I install?
Does the person I send the link to need an AgentDoc account?
What if I want the doc to stay private?
Does the agent count as a paid seat?
I'm not technical — is there a way to install without the terminal?
What does this cost?
One line. Zed ships links.
No new app. No account ceremony. Just ask Zed to publish, and send the URL.
npx -y @agentdoc/cli install zed