Skip to main content
You can launch a guided setup directly from the Spur app. Go to Integrations → MCP and click Setup to open a step-by-step modal for your platform.

Server details

Use these settings for any client that supports remote Model Context Protocol (MCP) servers: When you connect with OAuth for the first time, your browser opens so that you can authorize access to your Spur account. To connect without signing in, use an API key instead.

Cursor

Click the button to install Spur directly in Cursor, or copy the deep link below and paste it into your browser address bar. Install MCP Server

Claude Code

Run this command in your terminal:
Open Claude Code, run /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:
Complete the OAuth flow in your browser. Run 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.
1

Copy the server URL

2

Open connector setup

In Claude web or Desktop, open Customize → Connectors. Click Add, then choose Custom → Web.
3

Add Spur

Name the connector Spur, paste the server URL, and click Continue.
4

Authorize the connection

Review the detected authentication settings and finish adding the connector. Sign in to Spur when Claude opens the authorization flow.
On Claude Team and Enterprise plans, an Owner or Primary Owner must enable the connector under Organization settings → Connectors before members can use it. See Claude’s connector guide for the current setup and authentication options.

GitHub Copilot in VS Code

1

Open the MCP server section

Make sure the GitHub Copilot extension is installed. Open the Copilot panel and navigate to the MCP Servers section.
GitHub Copilot extension with MCP Server section
2

Add a new server

Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows/Linux) and type MCP: Add Server.
MCP: Add Server in the Command Palette
3

Select HTTP transport

Select HTTP (HTTP or Server-Sent Events).
Selecting HTTP transport type
4

Enter the server URL

Set the URL to https://app.spurtest.com/api/mcp.
Entering the Spur MCP server URL
5

Name the server

Enter a server name. Spur is recommended.
Naming the MCP server
6

Authenticate

Complete the OAuth authorization flow. Your browser opens so that you can authorize access to your Spur account.

ChatGPT

1

Open settings

Select Settings from the drop-down menu.
Open the ChatGPT settings menu
2

Navigate to advanced settings

Click Advanced Settings under the Apps tab.
Advanced Settings under the Apps tab
3

Enable developer mode

Toggle Developer mode on.
Enable developer mode
4

Create a new app

Click Create app.
Create a new app
5

Enter the MCP URL

Set the URL to https://app.spurtest.com/api/mcp.
Enter the Spur MCP URL
6

Authorize the Spur app

Complete the OAuth authorization flow. On Spur’s consent page, review the permissions to view tests and test results, run tests on your behalf, and create and manage tests.
7

Confirm the new app

Verify the app was created successfully.
Confirm the new app
8

Select Spur in Connectors

Select Spur from the Connectors list.
Choose Spur in the Connectors list
9

Start prompting

You’re all set. Start using Spur through ChatGPT.
Prompting ChatGPT with Spur

Gemini CLI

Run this command to add Spur to your user configuration:
Start Gemini CLI, run /mcp auth spur, and complete the OAuth flow in your browser.

Windsurf

1

Open the MCP configuration

In Cascade, click MCPs, or go to Windsurf Settings → Cascade → MCP Servers. Open the raw mcp_config.json file.
2

Add Spur

Add spur to the existing mcpServers object:
3

Authenticate

Save the file, connect to Spur, and complete the OAuth flow in your browser.

Zed

1

Open your settings file

Run zed: open settings file from the command palette.
2

Add Spur

Add spur to the existing context_servers object:
3

Authenticate

Save the file. Zed prompts you to complete the OAuth flow in your browser.

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: Both keys start with spur_mcp_.

Generate a key

1

Open the setup modal

In the application you want to connect, go to Integrations → MCP and click Setup.
2

Choose API key

Select API key (no OAuth) at the bottom of the platform list.
3

Generate a key

Under Generate an API key, find Your application key or Bot key and generate the key you need.
4

Add Spur to your client with the key

Follow the setup instructions for your client in the modal. They use the key you just generated.
Your client sends the key in an Authorization: Bearer header. Replace <key> with the key you generated. For Claude Code, run:
For other clients, add the header to the client’s user-level MCP config, not to a file in your repository. For Cursor, that file is ~/.cursor/mcp.json:
In Cursor, you can also keep the key out of the file. Store it in an environment variable, such as 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.
Only admins can change the bot key. If you can’t regenerate or revoke it, ask an admin on your account. See User Roles.

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.

Verify the connection

Open your client’s MCP server list and confirm that Spur is connected and its tools are available.