Zed
Connect Part3 to the Zed editor's MCP support.
Zed has built-in MCP support under its Context Servers feature. Add Part3
in settings.json.
Locate the config file
| OS | Path |
|---|---|
| macOS | ~/.config/zed/settings.json |
| Windows | %APPDATA%\Zed\settings.json |
| Linux | ~/.config/zed/settings.json |
You can also open it from the command palette: cmd-shift-p → zed: open
settings.
Add the MCP server
{
"context_servers": {
"part3": {
"source": "custom",
"command": null,
"args": [],
"env": {},
"url": "https://mcp.part3.io"
}
}
}HTTP MCP support
Zed's HTTP MCP support is the path you want. If your Zed install only exposes
the command-based stdio interface, run a local MCP HTTP-to-stdio bridge or
upgrade Zed.
No header, no secret. Zed opens a browser on first use to sign in and approve access.
Prime-only access
MCP is currently limited to users who are a Project Prime on at least one project, plus super-duper-admins. Non-Primes will see an access-denied page on the consent screen.
Verify
Open Zed's assistant panel. The part3 server should appear with its tools
listed under the context picker.
Troubleshooting
See the Claude Code troubleshooting section — the causes and fixes apply to Zed as well.