Skip to main content

Connect Rshift MCP in Cursor

B
Written by Binbin Shen

Connect Rshift MCP in Cursor

Cursor can connect to Rshift through its MCP settings. Use the JSON config generated by Rshift whenever possible to avoid header formatting mistakes.

Before you start

  1. Open the AI page for the current workspace in Rshift.

  2. Confirm that MCP is enabled.

  3. Copy the JSON config.

  4. If the JSON does not include the full key, rotate the key and copy it again.

Add the server

  1. Open Cursor Settings.

  2. Go to Tools & MCP.

  3. Click New MCP Server so Cursor opens mcp.json.

  4. Paste or merge the config below.

  5. Save the file, then enable or refresh rshift in Cursor's MCP list.

Project config usually lives in .cursor/mcp.json; global config usually lives in ~/.cursor/mcp.json. If a config file will be committed to a repository, do not put the real key in that project file.

{
  "mcpServers": {
    "rshift": {
      "url": "https://mcp.rshift.com/pentair/",
      "headers": {
        "Authorization": "Bearer <your MCP key>"
      }
    }
  }
}

If you do not want plaintext keys in the file, use Cursor's supported config interpolation or environment-variable flow. The final request still needs to send Authorization: Bearer <MCP_KEY>.

Verify the connection

  1. Confirm that rshift is enabled in Cursor's MCP server list.

  2. Check that Rshift tools appear in the available tools list.

  3. Test with a read-only tool before running anything that writes or publishes.

Common issues

  • Saved config does not take effect: refresh MCP servers or restart Cursor.

  • JSON error: check commas, quotes, and braces.

  • You cannot find the error: open Cursor's Output panel and select MCP Logs.

  • Tool call fails: confirm the workspace plan, MCP state, and related platform integrations.

Security

Do not commit Cursor MCP config files to your repository. Remove the Authorization value before sharing config snippets.

Did this answer your question?