Install in Cursor
Add the Spinrun gateway to Cursor for run and Build surfaces.
Run surface
1. Edit the MCP config
Add this server block to Cursor's MCP configuration file, then restart it — or run spinrun install cursor and let the CLI merge it for you.
{
"mcpServers": {
"spinrun": {
"url": "https://spinrun.ai/mcp",
"headers": {
"x-spinrun-client": "cursor"
}
}
}
}Fallback — If it asks for a key instead: If Cursor asks for a credential instead of opening a browser, add a headers block with your key.
{
"mcpServers": {
"spinrun": {
"url": "https://spinrun.ai/mcp",
"headers": {
"x-spinrun-key": "YOUR_API_KEY",
"x-spinrun-client": "cursor"
}
}
}
}2. Authorize in your browser
There is no key in that block on purpose. Cursor 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 Cursor's MCP configuration file, then restart it — or run spinrun install cursor --build and let the CLI merge it for you.
{
"mcpServers": {
"spinrun-build": {
"url": "https://spinrun.ai/mcp/build",
"headers": {
"x-spinrun-client": "cursor"
}
}
}
}2. Authorize in your browser
There is no key in that block, and there is no key form of it. Cursor 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.