Set up Spur MCP in 5 minutes

Connection steps

1. Create an API key for the workspace that the MCP client should access.
2. Set the MCP URL to the endpoint shown below.
3. If your client supports OAuth, choose the sign-in option and approve the connection with your Spur account.
4. If your client supports custom headers, configure Bearer authentication using your key.
5. If your client cannot set custom headers and has no OAuth support, append ?api_key=YOUR_KEY to the MCP URL and use No auth.
6. Run tools/list and confirm the expected tool names are returned.
7. Run one tools/call request and verify success and error behavior.

Codex app settings

• Transport: Streamable HTTP
• URL: https://api.spurnow.com/mcp
• Bearer token env var: use the variable name, not the literal key
• Accept header: application/json, text/event-stream

Claude custom connector settings

• Connector type: Remote MCP server
• Authentication: Sign in now (OAuth)
• Server URL: https://api.spurnow.com/mcp
• Approve the connection once, in the browser, with your Spur account

Claude signs in through Spur's OAuth flow (PKCE, dynamic client registration), so no API key goes in the connector URL. If you still need a key (an older client, or a connector that cannot sign in), use https://api.spurnow.com/mcp?api_key=YOUR_SPUR_API_KEY with authentication set to No auth, and rotate that key regularly.

Connect more than one Spur account in Claude

One Claude connector links to one Spur workspace. Claude will not accept a second connector with the same URL, and it says so: “A connector with this URL already exists in your organization.” Give each connector its own URL by appending a workspace_id query parameter:

https://api.spurnow.com/mcp?workspace_id=YOUR_WORKSPACE_ID

1. In Spur, switch to the client's workspace and open Settings › MCP. Copy the Workspace ID shown at the top.
2. In Claude, go to Settings › Connectors › Add custom connector. Name it after the client (Spur - Client A, Spur - Client B) and paste https://api.spurnow.com/mcp?workspace_id= followed by that ID.
3. Set authentication to Sign in now. Before you click Connect, make sure Spur is still switched to that client's workspace: the connector links to whichever workspace is open in Spur when you approve. The approval screen names that workspace, so check it before you approve.
4. Repeat for each client: switch Spur to their workspace, then add the connector with their workspace ID.
5. In a chat, turn on only the connectors you need and tell Claude which client you are working on.

The workspace_id value does not choose the workspace on Spur's side: the workspace open in Spur when you approve in step 3 does. The parameter is there to make each connector's URL different, so any value unique to that connector works. If you cannot see the client's workspace ID, use a sequence number instead, for example ?workspace_id=2.

Validate with JSON-RPC

Expected tool names from tools/list:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list",
  "params": {}
}

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "contact_create",
    "arguments": {
      "firstName": "MCP",
      "lastName": "Tester",
      "number": "919876543210",
      "email": "mcp.tester@example.com"
    }
  }
}