Connecting Claude Desktop to Xurrent MCP

How to configure Claude Desktop to connect to the Xurrent MCP server using the mcp-remote bridge package.

The Xurrent MCP server is a remote server hosted by Xurrent. You connect to it from Claude Desktop using the mcp-remote bridge package, which proxies your local Claude Desktop client to the hosted endpoint.

Prerequisites

• Claude Desktop installed. Download from claude.com/download or your company's app catalog.
• Node.js 20.18.1 or higher (Node 22 LTS recommended). Check with node -v in a terminal. If you're below this version, see Troubleshooting before continuing.
• A Xurrent Personal Access Token (PAT) with Sera AI enabled on the account. The token must resolve to a support domain account. If your user belongs to a support domain account, generate the PAT there. If your user belongs to a Directory Account, either use a user in the support domain account or pass the account explicitly with the X-Xurrent-Account header (see Configuration below). See Authentication and PAT Setup.

Configuration

Open your Claude Desktop config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the xurrent-mcp block to your mcpServers object, using the endpoint that matches your region and environment.

The Xurrent MCP server is hosted per region. Your MCP host matches your API host: the Global region has no region segment, and every other region inserts its code (for example ch for Switzerland). Production Global uses .com, Demo uses -demo.com, and QA uses .qa.

Production endpoints

Demo and QA follow the same regional pattern. Demo Global is https://mcp.xurrent-demo.com/mcp and QA Global is https://mcp.xurrent.qa/mcp. For a non-Global region, insert your region code the same way, for example https://mcp.ch.xurrent.qa/mcp for QA in Switzerland.

Use this block, replacing the placeholder values:

{
  "mcpServers": {
    "xurrent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "YOUR_REGIONAL_MCP_ENDPOINT",
        "--header",
        "Authorization: Bearer YOUR_PAT_HERE"
      ]
    }
  }
}

Replace YOUR_REGIONAL_MCP_ENDPOINT with the full URL from the table above, for example https://mcp.ch.xurrent.com/mcp. Replace YOUR_PAT_HERE with your Personal Access Token.

Note on the npx path. Claude Desktop does not inherit your terminal's PATH. If you installed Node via nvm or Homebrew, a bare npx command will fail to launch with the error "No such file or directory."

Find the absolute path to npx by running this in a terminal (use where npx on Windows):

which npx

Then use the full path it returns as the command value. On macOS it looks like this:

"command": "/Users/<you>/.nvm/versions/node/v22.22.3/bin/npx"

On Windows, double the backslashes so the JSON stays valid:

"command": "C:\\Program Files\\nodejs\\npx.cmd"

You can run multiple connections side by side, for example your Production and QA environments at once. Give each a different key (xurrent-mcp and xurrent-mcp-qa) with the matching endpoint from the table.

Fully quit Claude Desktop (Cmd+Q on macOS, not just close the window) and relaunch.

Verifying the connection

After relaunching, click the tools icon in Claude Desktop's chat input. You should see the Xurrent tools listed. Seeing the tools confirms the bridge connected to the server. It does not confirm that your token is authorized. To confirm that, run a real query, for example: "What are my open requests in Xurrent?" If you get data back, you are connected.

If the tools appear but a query returns a 403 error, the problem is not your Claude Desktop config. It is the token or the account. Check that the PAT resolves to a support domain account and that Sera AI is enabled on that account. See Authentication and PAT Setup and Troubleshooting.

A few things to know

• There is no @xurrent/mcp-server npm package. The Xurrent MCP server is remote, not a local package. Use mcp-remote as shown above.
• Authentication is via Bearer token in the Authorization header. The XURRENT_API_TOKEN and XURRENT_ACCOUNT environment variables won't work. To target a specific account, which is required if your PAT is from a Directory Account, add a second header in the args:

  "--header",
  "X-Xurrent-Account: YOUR_SUPPORT_DOMAIN_ACCOUNT_ID"

If something isn't working, see the Troubleshooting guide.