Scrubby

Zed

Connect Scrubby to Zed's Agent Panel via context_servers. Zed's AI gets your codebase's domains, conventions, and history through MCP.

Zed exposes Model Context Protocol servers as context servers in its Agent Panel. Adding Scrubby gives Zed’s AI assistant the same codebase intelligence layer that Claude Code, Cursor, Windsurf, and VS Code use — without leaving your editor.

Setup

1. Add the context server

Open Zed’s settings (cmd-, on macOS, ctrl-, on Linux) and add a context_servers entry:

{
  "context_servers": {
    "scrubby": {
      "url": "https://mcp.scrubby.ai/mcp"
    }
  }
}

2. Authenticate

Because the entry has no headers field with an Authorization token, Zed will trigger the standard MCP OAuth flow on first connect. Sign in with the GitHub account you used for Scrubby.

3. Verify the server is active

Open the Agent Panel and look for Scrubby in the settings view. The indicator dot next to its name should be green, with a tooltip reading “Server is active.”

4. Index your repository

From the Agent Panel, ask Zed’s assistant to index:

"Index this repo with Scrubby — it's owner/repo-name."

Indexing takes 1–3 minutes.

Tool access

The full tool list is documented in the MCP Tools Reference. Zed’s AI assistant reads the tool descriptions and decides when to call them.

Notes

  • Remote URL vs local command. Scrubby is a remote HTTP MCP server, so you use "url" rather than "command" and "args". The command/args form is for local stdio-based MCP servers.
  • OAuth handled by Zed. If no Authorization header is configured, Zed walks you through the MCP OAuth flow automatically. You don’t need to set up tokens manually.
  • Settings live in your Zed profile. Unlike per-project files like .cursor/mcp.json or .vscode/mcp.json, Zed’s context_servers live in your user settings. Add Scrubby once and it’s available in every project you open.

Troubleshooting

See Editor Not Connecting. Quick fixes:

  • Indicator dot is red or yellow — click on the server name in the Agent Panel settings view to see the connection error. Common cause is OAuth not completed.
  • Tools not exposed in Assistant — reload your Zed settings (or restart Zed) after editing settings.json.
  • OAuth never finishes — check that your default browser is reachable. You can also visit the Scrubby dashboard to log out and re-authenticate from Zed.

Last updated