Server details
Use these settings for any client that supports remote Model Context Protocol (MCP) servers:Cursor
Click the button to install Spur directly in Cursor, or copy the deep link below and paste it into your browser address bar.Claude Code
Run this command in your terminal:/mcp, and complete the OAuth flow.
Codex
Codex CLI and the Codex IDE extension share the same MCP configuration. Run these commands in your terminal:codex mcp list or /mcp in a Codex session to verify the connection.
Claude Desktop and Claude.ai
The Claude Desktop / .ai tab under Spur’s Integrations → MCP shows the server URL and a link to Claude’s connector setup.Copy the server URL
Open connector setup
Add Spur
Authorize the connection
GitHub Copilot in VS Code
Open the MCP server section

Add a new server
Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows/Linux) and type MCP: Add Server.
Select HTTP transport

Enter the server URL
https://app.spurtest.com/api/mcp.
Name the server

Authenticate
ChatGPT
Open settings

Navigate to advanced settings

Enable developer mode

Create a new app

Enter the MCP URL
https://app.spurtest.com/api/mcp.
Authorize the Spur app
Confirm the new app

Select Spur in Connectors

Start prompting

Gemini CLI
Run this command to add Spur to your user configuration:/mcp auth spur, and complete the OAuth flow in your browser.
Windsurf
Open the MCP configuration
mcp_config.json file.Add Spur
spur to the existing mcpServers object:Authenticate
Zed
Open your settings file
Add Spur
spur to the existing context_servers object:Authenticate
Other MCP clients
If your client supports remote Streamable HTTP servers and OAuth, use the server details above. If it can’t complete an OAuth sign-in, use an API key. If it only supports local command-based servers, use this command through its MCP configuration:API key (no OAuth)
Use an API key when the client can’t complete a browser sign-in: CI jobs, bots, headless agents, cloud agents, and other automations. The key replaces the OAuth step, so nothing opens in a browser. A key works on one application only. Because each application has its own keys, you can attach different Claude instances (or other agents) to different applications at the same time. Each instance only sees the application its key belongs to.Key types
Spur offers two keys for each application:spur_mcp_.
Generate a key
Open the setup modal
Choose API key
Generate a key
Add Spur to your client with the key
Authorization: Bearer header. Replace <key> with the key you generated.
For Claude Code, run:
~/.cursor/mcp.json:
SPUR_MCP_KEY, and write the header as "Authorization": "Bearer ${env:SPUR_MCP_KEY}".
Under each key, Regenerate key replaces it with a new one and Revoke turns it off. After you regenerate a key, update it everywhere you used it.
Keep your keys secret
A key grants access to its application without any sign-in, so treat it like a password:- Store it in your CI provider’s secret store or a secrets manager. Don’t commit it to a repository, paste it into a prompt, or share it in chat.
- Use the bot key for shared automations, so jobs don’t run as one person.
- Use a separate application’s key for each agent that should only touch that application.
- If a key leaks, click Revoke, or click Regenerate key and update your automations with the new key.
