Connecting Claude Desktop to Xurrent MCP

The Xurrent MCP server is a remote server hosted by Xurrent. There are two ways to connect Claude Desktop to it.

• Add it as a connector and sign in. The recommended route. No Node.js, no configuration file, and no token to paste.
• Use the mcp-remote bridge. A local Node package that proxies Claude Desktop to the hosted endpoint, authenticating with a Personal Access Token. Use this if your version of Claude Desktop cannot add a remote connector.

Endpoints

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.

Option 1: Add it as a connector and sign in

Prerequisites. Claude Desktop, and Sera AI enabled on the Xurrent account you are connecting to. An account administrator enables it under Settings, Account Settings, Sera AI.

On Claude Team and Enterprise plans, only an organization Owner can add a custom connector. The Owner adds the Xurrent MCP endpoint once, under Organization settings, Connectors, and members then select it and sign in individually. On Pro and Max plans you add the connector yourself, as described below.

1. In Claude Desktop, open Settings and go to Connectors.
2. Choose to add a custom connector. If your organization Owner has already added Xurrent, select it instead and continue from step 4.
3. Enter the Xurrent MCP endpoint for your region and environment, from the table above.
4. Claude Desktop discovers the Xurrent authorization server and registers itself. A Xurrent sign-in page opens.
5. Sign in as you normally would, including through single sign-on if your account uses it, then approve the access being requested.

That is the whole setup. There is no token to generate and no file to edit. Claude Desktop holds a short-lived access token and refreshes it in the background. See MCP Authentication for what the sign-in grants.

Option 2: The mcp-remote bridge

Use this only if your Claude Desktop cannot add a remote connector. It needs Node.js and a Personal Access Token.

Prerequisites

• Node.js 20.18.1 or higher (Node 22 LTS recommended). Check with node -v. If you are below this version, see Troubleshooting before continuing.
• A Xurrent Personal Access Token that resolves to a support domain account. See MCP Authentication.

Open your Claude Desktop config file:

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

Add the block below, replacing the placeholders:

{
  "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, and 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 will fail to launch with "No such file or directory".

Find the absolute path to npx (use where npx on Windows):

which npx

Then use the full path as the command value. On macOS:

"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 several connections side by side, for example Production and QA at once. Give each a different key (xurrent-mcp and xurrent-mcp-qa) with the matching endpoint.

Fully quit Claude Desktop (Cmd+Q on macOS, not just closing the window) and relaunch. The config is only re-read on a full restart.

Verifying the connection

Click the tools icon in Claude Desktop's chat input. You should see the Xurrent tools listed. Seeing the tools confirms the connection reached the server; it does not confirm you are authorized. To confirm that, run a real query, for example "What are my open requests in Xurrent?" If data comes back, you are connected.

If the tools appear but a query returns a 403, the problem is the account or the credential, not the client setup. Check that Sera AI is enabled on the account, and that a PAT, if you used one, resolves to a support domain account.

A few things to know

• There is no @xurrent/mcp-server npm package. The Xurrent MCP server is remote, not a local package.
• With the bridge, authentication is a Bearer token in the Authorization header. The XURRENT_API_TOKEN and XURRENT_ACCOUNT environment variables do not 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"

• Most of the Node and npx problems in Troubleshooting apply only to the bridge. Connector sign-in avoids them entirely.

Related

See MCP Authentication for both credential routes, Available Tools and Capabilities for what you can ask for, and Troubleshooting if something is not working.