Use with AI

Add a connection in developer mode. ChatGPT registers its own OAuth client, so there is no client id to type.

Paste this

No config file. This client is set up in its own settings screen.

Where to go

1. Open Settings, then Security and login, and turn on Developer mode.
2. Open chatgpt.com/plugins and choose the plus button.
3. Give the connection a name and a description.
4. Under Connection, paste the endpoint including its /mcp path.
5. Create the connection.
6. Review the tools and metadata discovered from the server.

Sign in

ChatGPT registers its own OAuth client with the server, so there is no client id or secret to type.

Who can use it

Developer mode must be on. The vendor says its availability can depend on account and workspace policy.

If it fails

A published plugin keeps the reviewed tool metadata it was approved with. A developer mode connection has a Refresh action for when the tools change.

We have not walked the in-product flow ourselves. These are the vendor’s published steps as of the review date, and the client registration comes from its plugin auth page (developers.openai.com/plugins/build/auth).

Streamable HTTP. The URL goes in the Connection field.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add a custom connector. This path signs in through the browser and takes no manual header.

Paste this

No config file. This client is set up in its own settings screen.

Where to go

1. Open Customize, then Connectors.
2. Choose the plus button, then Add custom connector.
3. Paste the RaiderRouter endpoint as the remote MCP server URL.
4. Skip Advanced settings, then choose Add.
5. Enable it for a conversation from the plus button in the chat, under Connectors.
6. On Team and Enterprise an Owner adds it under Organization settings, then Connectors.
7. That Owner chooses Custom, then Web, and members choose Connect to sign in.

Sign in

Claude runs the sign-in itself and takes no manual header. Team and Enterprise members choose Connect.

Who can use it

Free, Pro, Max, Team and Enterprise, on the web, Claude Desktop, Cowork and the mobile apps. Free accounts get one custom connector. Team and Enterprise need an Owner first.

If it fails

A URL only your own machine can reach will fail, because the request comes from Anthropic servers. A server on a private network, behind a VPN, or blocked by a firewall will not connect.

The connection is made from Anthropic servers rather than from your own machine.

Streamable HTTP. The URL goes in the custom connector URL field.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add the same custom connector the web client uses, from the desktop settings window.

Paste this

Where to go

1. Open Settings, then Connectors.
2. Add the same custom connector the web client uses, and paste the endpoint.
3. Approve the sign-in, then restart the client if tools do not appear.
4. To connect from your own machine instead, use the file below.
5. On macOS the file is at ~/Library/Application Support/Claude/claude_desktop_config.json.

Or paste this: Local bridge

{
  "mcpServers": {
    "raiderrouter": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://raiderrouter.com/mcp",
        "--transport",
        "http-only"
      ]
    }
  }
}

Sign in

Choose Connect on the connector, or let mcp-remote open the sign-in.

Who can use it

Custom connectors follow the same account as the web client. The file path is per machine.

If it fails

Edits to the file take effect only after a full restart of Claude Desktop.

Anthropic routes a server with a public URL to the connector. Its pages name the menu both Settings then Connectors and Customize then Connectors; it is one connector list. The file locations and the bridge block come from the mcp-remote README, not from Anthropic.

Streamable HTTP. The URL goes in the custom connector URL field, or the mcp-remote argument in the file.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add the URL, then approve RaiderRouter when Claude opens your browser.

Where to go

1. Run the command below in the project you want the server in.
2. Add --scope user to reach it from every project on this machine.
3. Add --scope project to share it with the repository.
4. Then sign in as described below.

Paste this

claude mcp add --transport http raiderrouter https://raiderrouter.com/mcp

Or paste this: Bearer fallback

claude mcp add --transport http raiderrouter https://raiderrouter.com/mcp --header "Authorization: Bearer YOUR_TOKEN"

Sign in

Run /mcp in a session, or run claude mcp login raiderrouter. Claude opens your browser.

Who can use it

Any Claude Code account. Project scope shares the server with the repository.

If it fails

A .mcp.json entry with a url and no type key is read as a local command and skipped. Set the type key to http.

Confirm with claude mcp list. Registered it as raider before 2026-09-10? Use that name in the login command.

The endpoint

Streamable HTTP. The URL goes in the argument after the server name.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Register RaiderRouter, then sign in through the browser.

Where to go

1. Run the first line to register the server.
2. Run the second line to open the browser sign-in.
3. Confirm the registration with codex mcp list.

Paste this

codex mcp add raiderrouter --url "https://raiderrouter.com/mcp"
codex mcp login raiderrouter

Or paste this: Bearer environment-variable fallback

[mcp_servers.raiderrouter]
url = "https://raiderrouter.com/mcp"
bearer_token_env_var = "RAIDER_MCP_TOKEN"

Sign in

Run codex mcp login raiderrouter, then approve in the browser.

Who can use it

Any Codex CLI account.

If it fails

Two [mcp_servers.raiderrouter] tables in config.toml is a parse error for the whole file. Edit the one codex mcp add wrote, or paste this one instead of running it. If the server is missing from a session, run codex mcp list and check the name you registered.

Registered it as raider before 2026-09-10? Use that name in the login command. The bearer table replaces the [mcp_servers.raiderrouter] table codex mcp add wrote; keep one, not both. Set RAIDER_MCP_TOKEN in the environment Codex runs in. The ChatGPT desktop app, the Codex CLI and the IDE extension share this configuration.

The endpoint

Streamable HTTP. The URL goes in the --url argument.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add one entry to the MCP configuration file, then let Cursor open the sign-in.

Where to go

1. Create the file named below in your project, or in your home folder for every project.
2. Paste the block below.
3. Cursor runs the sign-in itself for a server that requires it.

Paste this

{
  "mcpServers": {
    "raiderrouter": {
      "url": "https://raiderrouter.com/mcp"
    }
  }
}

Sign in

Cursor states OAuth support for servers that require it and runs the sign-in itself. No header is needed.

Who can use it

Any Cursor account that can edit its own MCP configuration file. An enterprise team with an MCP allowlist must list this server URL, or it is blocked.

If it fails

Adding a type key, or pointing at the /sse path, fails. This server answers 404 there.

The global file is ~/.cursor/mcp.json and covers every project.

The endpoint

Streamable HTTP. The URL goes in the url key.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add one entry to the workspace MCP file, then start the server from the palette.

Where to go

1. Create the file named below in your workspace.
2. Paste the block below.
3. Run MCP: List Servers, choose the server, then start it.
4. Trust the server when VS Code asks the first time it starts.

Paste this

{
  "servers": {
    "raiderrouter": {
      "type": "http",
      "url": "https://raiderrouter.com/mcp"
    }
  }
}

Sign in

VS Code’s configuration reference documents the browser sign-in for an entry carrying an oauth block with a client id. It shows the bare entry as unauthenticated. Use the bearer header if no browser opens.

Who can use it

Organisations can centrally manage access to MCP servers through GitHub policies.

If it fails

The wrapper key here is servers, not mcpServers. An Agent Host session does not read .vscode/mcp.json, so use a workspace .mcp.json or ~/.copilot/mcp-config.json there.

A user-level file covers every workspace and is edited from the palette. The headers and oauth fields are in the MCP configuration reference (code.visualstudio.com/docs/agents/reference/mcp-configuration).

The endpoint

Streamable HTTP. The URL goes in the url key.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add one entry with the streamable HTTP type and your token in the header.

Where to go

1. Create a token above.
2. Open the MCP Servers icon in the Cline panel, then the Configure tab.
3. Choose Configure MCP Servers, which opens the settings file.
4. Paste the block below into that file.
5. Keep the type key. Without it Cline tries the older transport.

Paste this

{
  "mcpServers": {
    "raiderrouter": {
      "type": "streamableHttp",
      "url": "https://raiderrouter.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Sign in

There is no browser sign-in. Use the token, or bridge through mcp-remote instead.

Who can use it

Any Cline installation. The token carries the account, so keep the file private.

If it fails

Cline defaults to the older SSE transport, and this server answers 404 there. Keep the type key.

The Remote Servers tab adds the same server without JSON: name, URL, transport Streamable HTTP, then Add Server. The Cline command line keeps its own servers in ~/.cline/mcp.json.

The endpoint

Streamable HTTP. The URL goes in the url key.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add one context server to your settings file, then let Zed sign you in.

Where to go

1. Open your settings file with zed: open settings file. Or add the server from Settings, then AI, then MCP Servers with Add Server, then Add Remote Server.
2. Paste the block below inside context_servers.
3. Leave the headers block out, so the sign-in can run.

Paste this

{
  "context_servers": {
    "raiderrouter": {
      "url": "https://raiderrouter.com/mcp"
    }
  }
}

Sign in

Zed prompts for the standard MCP sign-in when the entry has no Authorization header.

Who can use it

Any Zed installation that can edit its own settings file.

If it fails

An Authorization header switches the sign-in off, and that header is sent as the credential.

Zed calls these context servers. The wrapper key is not mcpServers.

The endpoint

Streamable HTTP. The URL goes in the url key.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Windsurf is now Devin Desktop. This entry is documented for the older Cascade agent.

Less certain We have read this path rather than run it. Confirm it in the client documentation.

Where to go

1. Open the configuration file named below.
2. Paste the block below. The remote key is serverUrl, and url also works.
3. Restart the client, then check the server is listed in Cascade.
4. Confirm the current path in the client documentation before you rely on it.

Paste this

{
  "mcpServers": {
    "raiderrouter": {
      "serverUrl": "https://raiderrouter.com/mcp"
    }
  }
}

Sign in

Devin Desktop states OAuth support for each transport but documents no sign-in path. Use a token in a headers block if no browser opens.

Who can use it

The documented file covers the Cascade agent. A newer agent in the same client reads a different file. Once a team allowlists one MCP server, every server not on the list is blocked.

If it fails

A new tab may open the newer agent, which does not read this file. Check which agent is running.

Treat this entry as less certain than the other clients on this page.

The endpoint

Streamable HTTP. The URL goes in the serverUrl key.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Add RaiderRouter as a custom MCP connector in Grok.

Paste this

No config file. This client is set up in its own settings screen.

Where to go

1. Open grok.com/connectors.
2. Choose New Connector, then Custom.
3. Paste the RaiderRouter endpoint as the MCP server URL.
4. Complete the authentication Grok asks for.
5. Grok discovers the tools and makes them available in conversations.

Sign in

Grok asks for whatever authentication the server requires when the connector is added.

Who can use it

Connectors are available to all Grok users. Business and Enterprise need an admin to provision the connector in the cloud console first.

If it fails

The server must be reachable over the public internet. A server on your own machine needs a tunnel.

Grok makes the tools available in conversations itself. There is no per-conversation switch to turn on.

Streamable HTTP. The URL goes in the server URL field.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.

Bridge the endpoint into any client that runs a local command.

Where to go

1. Register the command below as a local MCP server in your client.
2. npx fetches mcp-remote on demand, so there is nothing to install first.
3. Create a token above for a client that cannot open a browser.
4. Send the token as an Authorization: Bearer header on every request.

Paste this

npx -y mcp-remote https://raiderrouter.com/mcp --transport http-only

Or paste this: Handshake check, with a token

curl -sS -X POST https://raiderrouter.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "initialize", "params": {"protocolVersion": "2026-07-28", "capabilities": {}, "clientInfo": {"name": "curl", "version": "1"}}}'

Sign in

mcp-remote runs the browser sign-in for clients that cannot. A token works instead.

Who can use it

No account gating. Any client that can run a local command can reach this.

If it fails

Without the Accept header naming both JSON and event streams the server answers 406.

Keep the token in a secret store or environment variable and never commit it. The mcp-remote README warns that Cursor, the Codex CLI and Claude Desktop on Windows mangle spaces inside args. Write the header as Authorization:${AUTH_HEADER} with the space inside the variable, or pass --header-file.

The endpoint

Streamable HTTP. The URL goes in the first argument after mcp-remote.

Client documentation · Reviewed 2026-09-11. Next review due 2026-12-10.