Skip to content

MCP troubleshooting

Why a client cannot connect or tools do not appear.

Updated View as Markdown

Common issues

  • The URL is not exactly https://mcp.rshift.com/mcp.
  • The signed-in account cannot access the workspace selected during OAuth.
  • MCP is disabled or unavailable on the workspace plan.
  • The current role or plan does not authorize the requested tool.
  • A required platform integration is not connected.
  • The client does not support OAuth for remote HTTP MCP servers.

Authorize again from the client after changing RShift accounts. Do not send OAuth authorization codes, access tokens, tool payloads, customer data, or private tool code to Support.

Navigation

Search for a question, a feature, or a task.

↑↓ to navigate↵ to openEsc to close