Zed
Connect Part3 to the Zed editor's MCP support.
Zed has built-in MCP support — it calls them context servers. Add Part3 in
settings.json.
Add the MCP server
Open your Zed settings from the command palette (cmd-shift-p → zed: open
settings). Add Part3 as a remote context server — for a remote server you
provide only a url:
{
"context_servers": {
"part3": {
"url": "https://mcp.part3.io"
}
}
}You can also add it through the UI: open the Agent Panel → Settings → Add Custom Server.
No header, no secret. Because no Authorization header is set, Zed runs the
standard MCP OAuth flow — it opens a browser on first use so you can sign in
and approve access (it stores the session in your system keychain, so you
won't be prompted again on restart).
If tools don't show up (older Zed / remote-OAuth bug)
Native remote (streamable-HTTP) MCP servers with OAuth are supported in
current Zed. On some builds, agents may only see the server's authenticate
tool — or a remote-OAuth server may not connect at all. If that happens,
bridge through a local stdio proxy with
mcp-remote:
{
"context_servers": {
"part3": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.part3.io"],
"env": {}
}
}
}mcp-remote performs the OAuth browser flow locally and proxies it to Part3's
HTTP endpoint. (Requires Node.js / npx on your PATH.)
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 Agent Panel → Settings. The part3 server should appear with a
green indicator dot ("Server is active"); its tools are then available to the
agent.
Troubleshooting
See the Claude Code troubleshooting section — the causes and fixes apply to Zed as well.