Install
Add to ~/.config/zed/settings.json:
{
"context_servers": {
"agentdoc": {
"command": {
"path": "npx",
"args": ["-y", "@agentdoc/mcp"]
}
}
}
}
Zed reloads the config live — no restart.
First run provisions an anonymous API key at ~/.agentdoc/mcp-key.json. No email, no OAuth.
What the assistant can do
"Publish the design doc we wrote this morning as
design/auth-flow." "Open the most recent version of the onboarding AgentDoc." "Fetch our deploy runbook and apply it here."
Create, update, publish, fork, and search — all via the same MCP server every other AgentDoc integration uses.
Sync editor rules across repos
Zed doesn't have a .cursorrules equivalent, but if your team keeps conventions in a shared markdown file, you can track it:
agentdoc init
agentdoc track docs/conventions.md --slug team-conventions
agentdoc pull
Quick start
# Paste the snippet above into ~/.config/zed/settings.json
# Zed picks it up live. Ask: "Publish this design doc as design/auth-flow."