Install in Zed
Add the Spinrun gateway to Zed for run and Build surfaces.
Run surface
1. Edit the MCP config
Add this server block to Zed's MCP configuration, then restart it.
{
"context_servers": {
"spinrun": {
"url": "https://spinrun.ai/mcp",
"headers": {
"x-spinrun-client": "zed"
}
}
}
}Fallback — If it asks for a key instead: Zed will not start the browser flow while a headers block is present, so this entry replaces the one above rather than adding to it.
{
"context_servers": {
"spinrun": {
"url": "https://spinrun.ai/mcp",
"headers": {
"x-spinrun-key": "YOUR_API_KEY",
"x-spinrun-client": "zed"
}
}
}
}2. Authorize in your browser
There is no key in that block on purpose. Zed opens a browser the first time it connects; choose a workspace there and you are done. You can revoke it any time from Settings → Applications.
Build surface
1. Edit the MCP config
This is the Build surface — it authors agents and workflows rather than running tools, and it accepts browser authorization only. Add this server block to Zed's MCP configuration, then restart it.
{
"context_servers": {
"spinrun-build": {
"url": "https://spinrun.ai/mcp/build",
"headers": {
"x-spinrun-client": "zed"
}
}
}
}2. Authorize in your browser
There is no key in that block, and there is no key form of it. Zed opens a browser the first time it connects; choose a workspace there. Tick "Build authorization" on the consent screen, or enable it later under Settings → Applications (workspace owners only). You can revoke it any time from Settings → Applications.