Skip to main content

MCP Gateway and tool connection troubleshooting

B
Written by Binbin Shen

MCP Gateway and tool connection troubleshooting

Rshift MCP Gateway gives each workspace a unified entry point for authorized marketing, content, monitoring, and analytics tools.

What you need

  1. A Rshift workspace with MCP enabled.

  2. The MCP URL from the workspace AI page, usually https://mcp.rshift.com/<workspace>/.

  3. The workspace MCP key. Newly generated or rotated keys are shown in full and should be copied into the target client immediately.

  4. A client that supports HTTP MCP servers and an Authorization header.

Client configuration formats differ. The JSON shown in Rshift works for clients such as Cursor that use mcpServers; VS Code uses servers, and Codex uses config.toml.

Client-specific guides

  • Claude Code: add Rshift with claude mcp add --transport http ... --header ....

  • Cursor: edit mcp.json in Tools & MCP and use the mcpServers config shape.

  • VS Code: add an HTTP server through MCP: Add Server or mcp.json; the top-level config is servers.

  • Codex: add a remote MCP server in config.toml under [mcp_servers.rshift].

  • ChatGPT: do not directly connect the general Rshift MCP Gateway today; it needs a ChatGPT-specific app / OAuth / scoped-tool flow.

Common issues

  • Your plan does not include a private MCP catalog.

  • MCP Gateway is not enabled for the workspace.

  • The MCP API key expired or was reset.

  • The tool is not authorized for the workspace.

  • A tool depends on a platform integration that is not connected yet.

  • The client does not support a custom Authorization header.

  • A config shape from one client is pasted into another client, such as using Cursor's mcpServers JSON in VS Code or Codex.

What to check

  1. Workspace plan and MCP entitlement.

  2. MCP Gateway enabled state.

  3. Whether the target tool appears in the catalog.

  4. Whether related platform accounts are connected.

  5. Whether your client uses the latest gateway endpoint.

  6. Whether the URL, header name, and header value match the Rshift page.

  7. Whether the configuration format matches the target client.

Key handling

The MCP key is a workspace-level key. It is not your login password or a platform account token. If an old key was stored only as a hash, Rshift cannot recover the plaintext value. Rotate the key when you need to see the full value again, then update every connected client.

Rshift Support can explain gateway status, tool availability, and error categories. Do not send MCP API keys, tool input/output payloads, customer data, or private tool code in Intercom.

Did this answer your question?