Connect an MCP client to RPScripts

Every client uses the same server URL and transport:

https://rpscripts.net/mcp

The public tools work right away. The first time you call a tool that needs your account (list_purchases, get_download_url, generate_script), the client opens the RPScripts login in your browser; approve the access and the call continues. Clients that support MCP authorization do this automatically. See Sign-in and permissions.

Claude (web and desktop)Copy Anchor Link

Open Settings → Connectors → Add custom connector, name it RPScripts and paste the server URL. Custom connectors are available on the Claude plans that offer them.

Claude CodeCopy Anchor Link

claude mcp add --transport http rpscripts https://rpscripts.net/mcp

Run /mcp inside Claude Code to sign in when you first use a private tool.

ChatGPTCopy Anchor Link

In Settings → Apps & Connectors → Advanced settings, turn on Developer mode, then create a connector with the server URL. ChatGPT handles the OAuth sign-in.

CursorCopy Anchor Link

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "rpscripts": { "url": "https://rpscripts.net/mcp" }
  }
}

Or open this install link in a browser with Cursor installed:

cursor://anysphere.cursor-deeplink/mcp/install?name=rpscripts&config=eyJ1cmwiOiJodHRwczovL3Jwc2NyaXB0cy5uZXQvbWNwIn0=

VS Code (GitHub Copilot)Copy Anchor Link

{
  "servers": {
    "rpscripts": { "type": "http", "url": "https://rpscripts.net/mcp" }
  }
}

Or from a terminal: code --add-mcp '{"name":"rpscripts","type":"http","url":"https://rpscripts.net/mcp"}'

WindsurfCopy Anchor Link

{
  "mcpServers": {
    "rpscripts": { "serverUrl": "https://rpscripts.net/mcp" }
  }
}

OpenCodeCopy Anchor Link

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rpscripts": { "type": "remote", "url": "https://rpscripts.net/mcp" }
  }
}

OpenCode detects the sign-in request and registers itself automatically.

Gemini CLICopy Anchor Link

{
  "mcpServers": {
    "rpscripts": { "httpUrl": "https://rpscripts.net/mcp" }
  }
}

Codex CLICopy Anchor Link

[mcp_servers.rpscripts]
url = "https://rpscripts.net/mcp"

Clients without remote MCP supportCopy Anchor Link

Clients that only start local (stdio) servers can reach RPScripts through the mcp-remote bridge:

{
  "mcpServers": {
    "rpscripts": { "command": "npx", "args": ["-y", "mcp-remote", "https://rpscripts.net/mcp"] }
  }
}

Test with the MCP InspectorCopy Anchor Link

npx @modelcontextprotocol/inspector --cli https://rpscripts.net/mcp --transport http --method tools/list

Without --cli, the Inspector opens a browser UI where you can call each tool and walk through the sign-in.

Older URLCopy Anchor Link

The first RPScripts MCP endpoint, https://rpscripts.net/api/mcp/, still works and serves the same tools. New setups should use https://rpscripts.net/mcp.