Troubleshooting

Start by identifying which kind of connection you have, because the failures are different.

• Signed in with OAuth, by adding the Xurrent MCP endpoint as a connector. Go to Sign-in and authentication below. None of the Node.js problems apply to you.
• The mcp-remote bridge, with a Personal Access Token in a config file. Any section can apply.

Sign-in and authentication

Every tool call returns a 403. Two causes account for almost all of these.

• Sera AI is not enabled on the account the MCP server connects to. An account administrator enables it under Settings, Account Settings, Sera AI. This is an account setting, not something you can fix in the client.
• The credential resolves to the wrong account. MCP expects a support domain account. If you are using a PAT created on a Directory Account, either create one in a support domain account, or pass the target account in the X-Xurrent-Account header.

The scope is missing or incomplete. A PAT needs the MCP scope with Tools, Resources, and Prompts all selected. Check that the scope was actually saved to the token, which means clicking Add Scope in the form. The order in which the actions were added is irrelevant, so there is no need to regenerate a token that already carries the right scope.

The sign-in window opens but never completes. Check that pop-ups are not blocked, and that any corporate proxy is not intercepting the redirect back to your client. If your account uses single sign-on, confirm you can sign in to Xurrent normally in a browser first.

It worked and now asks you to sign in again. Access is short-lived and refreshed automatically, so a repeated prompt usually means the session was ended deliberately, by you or an administrator. Signing in again restores it.

A 401 with the bridge. Verify the Authorization header value starts with Bearer including the trailing space, and that the token has not been disabled. Check under My Profile, then Personal Access Tokens. Note that Personal Access Tokens do not expire on their own, so a token that stopped working was disabled rather than aged out.

Server connects but no tools appear

This covers no tools at all. If tools appear but a call fails with a 403, see the section above instead.

• The credential is missing the MCP scope. See MCP Authentication.
• The PAT was disabled. Generate a new one.
• The tool list is cached. In Copilot Studio, re-save and republish the tool. In Claude Desktop, fully quit (Cmd+Q) and relaunch.

Bear in mind the tool list varies by account and by your roles, so a specific tool being absent is not necessarily a fault. See Available Tools and Capabilities.

Server connects then disconnects after about 30 seconds

Likely a network or proxy issue. The MCP connection is long-lived, and proxies that terminate idle connections after roughly 30 seconds will break it. If you are behind a corporate proxy or VPN, allowlist your regional MCP endpoint and confirm long-lived HTTPS connections are not being dropped.

Rate limiting or "too many requests"

The Xurrent MCP server enforces rate limits to protect platform stability. Heavy use across many concurrent users may hit them. If you hit limits regularly, contact your CSM to discuss your use case and expected volume.

mcp-remote bridge problems

Everything in this section applies only to the mcp-remote bridge. If you signed in with OAuth, none of it is relevant. Switching to connector sign-in removes this whole class of problem.

"Failed to spawn process: No such file or directory"

Claude Desktop cannot locate the npx binary, because Node is not installed or was installed via nvm or Homebrew on a path Claude Desktop does not inherit.

1. Confirm Node resolves in a terminal: node -v (must be 20.18.1 or higher).
2. Get the absolute path: which npx
3. In your config, replace "command": "npx" with that full path, for example "command": "/Users/<you>/.nvm/versions/node/v22.22.3/bin/npx".
4. Fully quit Claude Desktop (Cmd+Q) and relaunch.

"ReferenceError: File is not defined"

Node.js is below 20.18.1, which mcp-remote requires. Install Node 22 via nvm:

nvm install 22
nvm alias default 22

Then get the absolute path with which npx and use it as the command value, since Claude Desktop does not inherit your shell's nvm environment. Clear the stale cache with rm -rf ~/.npm/_npx and relaunch.

The log shows an old Node version at the bottom

The old version is still first on PATH. Uninstall it with nvm uninstall <old-version>, clear the cache with rm -rf ~/.npm/_npx, and relaunch.

Config changes do not take effect

Closing the window does not restart the app, and the config is only re-read on a full restart. On macOS use Cmd+Q or Claude, then Quit Claude. On Windows, right-click the system tray icon and select Quit.

"Server transport closed unexpectedly"

A generic message meaning the process exited. Look further up the log for the real error. Common causes are a Node version mismatch, a stale npx cache, or a malformed Authorization header such as a missing Bearer prefix or stray whitespace.

Where to find logs

Claude Desktop on macOS:

~/Library/Logs/Claude/mcp-server-<your-server-key>.log

Claude Desktop on Windows:

%APPDATA%\Claude\logs\mcp-server-<your-server-key>.log

The filename matches the key you used in your config. For the QA setup (xurrent-mcp-qa), the file is mcp-server-xurrent-mcp-qa.log.

Before sharing logs. If you use a PAT, scrub it first. It appears in plain text in the arguments of every log entry. Replace it with "Bearer REDACTED" before pasting into a ticket, a Slack message, or a document.

Still stuck?

Contact your CSM or open a request in Xurrent. Include:

• Which MCP client and version, and whether you signed in with OAuth or used a PAT
• Your Xurrent region and environment
• The full error message from the log, with any token scrubbed
• What you have already tried