@xurrent/imr-mcp-server

Connect Claude Desktop (or any MCP client) to Xurrent Incident Management in one command.

Quick Start

1. Get your API key

Log in to your Xurrent account → Profile → Account → API Keys and create or copy a key.

2. Configure your MCP client

Pick the client you use and add the config below.

Claude Desktop

Open your Claude Desktop config:

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

Add:

{
  "mcpServers": {
    "xurrent-imr": {
      "command": "npx",
      "args": ["-y", "@xurrent/imr-mcp-server"],
      "env": {
        "XURRENT_IMR_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Then fully quit (Cmd+Q on Mac) and reopen. The xurrent-imr server should appear under MCP connectors.

Claude Code (CLI)

Add the server to your project settings:

claude mcp add xurrent-imr -e XURRENT_IMR_API_KEY=YOUR_API_KEY -- npx -y @xurrent/imr-mcp-server

Or manually add to .claude/settings.json:

{
  "mcpServers": {
    "xurrent-imr": {
      "command": "npx",
      "args": ["-y", "@xurrent/imr-mcp-server"],
      "env": {
        "XURRENT_IMR_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Other MCP clients

Any MCP-compatible client can connect using the same config. The command is:

npx -y @xurrent/imr-mcp-server

Set the XURRENT_IMR_API_KEY environment variable to your API key.

Available Tools

Once connected, Claude can use these tools to query your Xurrent incidents:

| Tool | Description | |------|-------------| | list_teams | List all teams you have access to | | list_incidents | List incidents with filters (status, severity, team, date range) | | get_incident | Get full details for a specific incident | | list_incident_updates | Get the timeline/update history for an incident | | search_incidents | Search incidents by keyword | | get_current_on_call | Show who is currently on call |

Example Prompts

Try these in Claude Desktop after setup:

• "Show me all my teams"
• "List open critical incidents"
• "Show details for incident #42"
• "Who is on call right now?"
• "Search incidents related to database outage"
• "Show the timeline for incident #42"

Auto-Reconnect

If the connection to the MCP server drops (laptop sleep, network change, load balancer timeout), the package automatically restarts the connection within 1 second. You don't need to quit and restart Claude Desktop.

• Reconnects automatically on any unexpected disconnect
• Max 5 reconnects per minute to prevent infinite loops
• Clean shutdowns (e.g., quitting Claude Desktop) are not retried
• If reconnection fails repeatedly, a clear error message is shown in the Claude Desktop MCP logs

Requirements

• Node.js 18 or later
• A valid Xurrent API key

Troubleshooting

"XURRENT_IMR_API_KEY environment variable is required" Make sure the env block is set in your Claude Desktop config (see step 2 above).

Tools don't appear in Claude Desktop Fully quit Claude Desktop (Cmd+Q, not just close the window) and reopen.

401 Unauthorized Your API key is invalid or expired. Generate a new one from your Xurrent account settings.

Claude spins and doesn't respond after being idle The auto-reconnect handles most cases. If it persists, fully quit Claude Desktop (Cmd+Q) and reopen — this forces a fresh connection and session.

"Too many restarts — giving up" The MCP server may be unreachable. Check your network connection and verify the server is up. Restart Claude Desktop to try again.

License

© Xurrent Inc. All Rights Reserved.