Skip to content
All guides

Zed + AgentDoc

Zed context server entry. Publish docs inline from the editor with the built-in assistant.

2 min readGuide

Install (pick one line)

Technical — paste in your terminal:

npx -y @agentdoc/cli install zed

Merges the AgentDoc context server into ~/.config/zed/settings.json. Zed reloads config live — no restart.

Not technical — paste in Zed:

Set up AgentDoc for me: https://agentdoc.com/install/zed.md

The Zed assistant fetches the install markdown, edits settings.json, and tells you what it did.

Manual install

Add to ~/.config/zed/settings.json:

{
  "context_servers": {
    "agentdoc": {
      "command": {
        "path": "npx",
        "args": ["-y", "@agentdoc/mcp"]
      }
    }
  }
}

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

Every other agent

See agentdoc.com/connect.