Rocket MCP

The Model Context Protocol (MCP) is an open standard that lets AI tools connect to external services and take actions via structured tool calls. Rocket MCP connects your Rocket.net account to MCP-capable clients so you can manage Rocket resources through conversation instead of clicking through dashboards.

Why use MCP

Rocket MCP allows access to do anything you can do through the Rocket.net API but without having to write a single line of code. Good news, the Rocket.net platform is 100% API-driven so Rocket MCP has the power to do anything you need. You can simply ask Rocket MCP questions or give it commands and you can do many amazing things with your sites.

Examples:

• Change the PHP version on all your sites by asking “Please change the PHP version on all my Rocket.net sites to 8.4”
• Find your sites using the most disk space by asking “Which Rocket.net sites use the most disk space, show them in order of disk space used”
• Keep plugins up-to-date by asking “Find any out of date plugins on my Rocket.net sites. Show a table of what needs to be updated.”

Requirements

• A Rocket.net account
• Node.js on your computer (needed for npx and the mcp-remote bridge)

Need an account? Sign up at rocket.net/registration.php.

Get an access token (JWT)

Some clients (like Gemini CLI) are easiest to configure with a bearer token. You can generate a JWT by following the steps below.

How Rocket MCP works (high level)

Rocket exposes an MCP server over HTTP + Server-Sent Events (SSE). Many AI clients only support MCP servers that run as a local process, so we use mcp-remote as a local bridge that connects to Rocket’s SSE URL.

Step 1: Choose your authentication method

Rocket MCP supports passing credentials as request headers. The recommended approach is to provide ROCKETNET_USERNAME and ROCKETNET_PASSWORD headers so the server can obtain/refresh JWTs as needed.

Treat credentials like passwords: don’t commit them, don’t paste them into logs, and rotate them if they leak.

Step 2: Connect your AI client (recommended)

Add the following MCP server configuration to your client. This runs a local mcp-remote process which connects to Rocket’s SSE endpoint: https://mcp-staging.onrocket.cloud/sse.

{
  "mcpServers": {
    "rocket-net-sse": {
      "command": "npx",
      "args": [
        "mcp-remote", 
        "https://mcp-staging.onrocket.cloud/mcp", 
        "--transport",
        "http",
        "--header", "Authorization: Bearer YOUR_ACCESS_TOKEN_GOES_HERE"
      ]
    }
  }
}

Client-specific setup

Different clients store MCP settings in different places, but the goal is always the same: run mcp-remote locally and point it at Rocket’s SSE URL, passing your credentials as headers.

Cursor

In Cursor, add Rocket MCP through the MCP settings UI:

1. Open the command palette:
   • macOS: Cmd + Shift + P
   • Windows: Ctrl + Shift + P
2. Select View: Open MCP Settings
3. Add a new custom MCP server by pasting the configuration from Step 2, then save the mcp.json file.

Claude Desktop

Claude Desktop reads a local JSON config file. Add a mcpServers entry that runs mcp-remote.

Common config locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\\Claude\\claude_desktop_config.json

After updating the file, fully quit and reopen Claude Desktop.

Claude Code (terminal)

Claude Code typically manages MCP servers via a CLI command. If your install supports it, add Rocket MCP using an HTTP transport and pass headers for auth.

# Example shape (adjust to your CLI's exact flags):
claude mcp add --transport http rocket-net https://mcp-staging.onrocket.cloud/mcp \
  --header "Authorization: Bearer YOUR_ACCESS_TOKEN_GOES_HERE"

If your Claude Code build only supports local processes (no remote URLs), use the mcp-remote JSON config pattern shown above instead.

Gemini CLI

Gemini CLI can be configured with a direct MCP server URL and an Authorization bearer token. First, generate a JWT (see Getting started), then add it to your Gemini MCP config.

{
  "security": {
    "auth": {
      "selectedType": "oauth-personal"
    }
  },
  "mcpServers": {
    "rocket-net": {
      "url": "https://mcp-staging.onrocket.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Other clients

If your client supports MCP but you don’t see Rocket-specific docs for it, use one of these two patterns:

• Local process (most common): run npx with mcp-remote and the args shown above.
• Direct URL: set the MCP server URL to https://mcp-staging.onrocket.cloud/mcp and add Authorization: Bearer YOUR_ACCESS_TOKEN_GOES_HERE as a header.

Step 3: Confirm it’s working

After saving your MCP settings, restart your AI client (or reload its window), then try a simple request like:

• “List my Rocket.net sites using their MCP server.”
• “Show me my most recently created site.”
• “Purge cache for my primary domain.”

Troubleshooting

• Config changes don’t apply: fully quit and restart your AI client after editing MCP settings.
• Auth failures: double-check your Authorization header.
• npx prompts or version issues: make sure Node.js is installed and available on your PATH.