Skip to content

MCP Server Configuration: Endpoint, Tokens and Health Check

Xplorr runs the MCP server for you at https://mcp.xplorr.io/mcp. There is nothing to install, so configuration comes down to two values in your MCP client: the endpoint URL and your API token.

SettingValue
URLhttps://mcp.xplorr.io/mcp (with /mcp at the end)
TransportHTTP
HeaderAuthorization: Bearer xplorr_your_token_here

The Hosted MCP guide has ready to paste configs for Claude Desktop, Claude Code and Claude.ai.

Every request to the MCP server carries your own xplorr_ token in the Authorization header. The server uses it to look up your organization and role, so Claude sees exactly the data you see in the console.

Create tokens in the console under Settings, in the API Tokens section. The steps are in Create a token.

  • Name each token after where it is used, such as Claude Desktop or Laptop Claude Code. The list shows when each one was last used, which makes stale tokens easy to spot.
  • Set an expiry of 30 days, 90 days or 1 year unless you have a reason not to.
  • Revoke a token as soon as a machine is lost or a person leaves. Anything using it stops working immediately.

The server exposes a health endpoint at GET /health. It needs no token:

Terminal window
curl https://mcp.xplorr.io/health
{
"status": "ok",
"service": "xplorr-mcp",
"tools": 28,
"mode": "multi-tenant"
}

Use it to check the endpoint is reachable from your network before debugging a client config.

Can I use more than one token? Yes. Create one per client or machine so you can revoke them independently.

What happens if the token is invalid? The MCP server rejects the request with an unauthorized error. Check that the token starts with xplorr_, has no extra spaces, and has not expired or been revoked.

Can I run the MCP server myself? No. The MCP server reaches the Xplorr backend from inside Xplorr’s own infrastructure, so it is only offered as the hosted endpoint at https://mcp.xplorr.io/mcp.