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 custom headers, configure Bearer authentication using your key.
4. If your client cannot set custom headers (for example Claude custom connectors), append ?api_key=YOUR_KEY to the MCP URL and use No auth.
5. Run tools/list and confirm the expected tool names are returned.
6. 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: No auth
• Server URL: https://api.spurnow.com/mcp?api_key=YOUR_SPUR_API_KEY
• Use a dedicated API key for Claude and rotate it regularly

Claude custom connectors currently do not support manually setting Authorization headers. Use a dedicated low-privilege key when using URL query auth.

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"
    }
  }
}