Documentation

RankReactor Claude

RankReactor Claude setup: connect the SEO MCP server in Claude Desktop, the claude.ai custom connector, and Claude Code.

Every RankReactor plan, including Free, can connect an assistant and create a project API key. Free can generate its one lifetime article through an assistant (the same article as the dashboard). Ongoing generation needs a paid plan. UGC video needs Pro or Ultra.

Free includes 1 lifetime article, shared across the dashboard and any assistant. After that article is used, ongoing generation needs a paid plan.
Starter is $39/month and includes a 3-day trial.
Pro is $79/month.
Ultra is $159/month.
Read tools work on every plan. Refreshing metrics through an assistant needs Starter, Pro, or Ultra. Queuing a UGC video needs Pro or Ultra.

Claude can use RankReactor through a custom remote connector (claude.ai, Claude Desktop, and Cowork) or through Claude Code over HTTP. The server URL is https://www.rankreactor.ai/mcp.

claude.ai custom connector

Anthropic’s custom-connector docs say remote MCP is available on Claude, Cowork, and Claude Desktop for Free, Pro, Max, Team, and Enterprise. Free accounts are limited to one custom connector. Remote connectors are reached from Anthropic’s cloud, so the RankReactor URL must stay on the public internet.

Pro and Max

Open Customize → Connectors.
Click + , then Add custom connector.
Enter the remote MCP server URL https://www.rankreactor.ai/mcp.
Leave Advanced settings empty unless Anthropic asked you for a client id. RankReactor does not require you to type one.
Click Add.
When Connect RankReactorAI opens, paste the project key from Dashboard → API Key and choose Allow.
In a chat, open + → Connectors and enable RankReactor for that conversation.

Team and Enterprise

Only Owners can add a custom connector to the organization. Members then connect it themselves.

An Owner opens Organization settings → Connectors.
Click Add, hover over Custom, then select Web.
Add https://www.rankreactor.ai/mcp and finish with Add.
Each member opens Customize → Connectors, finds the custom connector, and clicks Connect.
Paste the project key on Connect RankReactorAI and choose Allow.

Claude Desktop

Official Anthropic docs treat remote MCP on Claude Desktop as the same custom-connector flow as claude.ai — the connection is brokered through your Claude account, not through a local URL in claude_desktop_config.json.

Add RankReactor under Customize → Connectors (or Organization settings → Connectors on Team and Enterprise), using the steps above.
claude_desktop_config.json (macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json) is the official file for local stdio servers. Anthropic’s current connector docs do not use that file for a hosted HTTPS MCP URL.
Local stdio servers in that file stay on your machine. They are not available in Cowork or claude.ai.

Claude Code

Claude Code’s official MCP guide registers a hosted server with claude mcp add --transport http. Run the command in your terminal, not inside a claude session.

claude mcp add --transport http rankreactor https://www.rankreactor.ai/mcp

That writes a local-scope entry (this project, your user). Use --scope user for every project, or --scope project to write .mcp.json in the repo root.

Run the add command above.
Check status with claude mcp list. A server that needs sign-in shows Needs authentication.
Start claude, run /mcp, select rankreactor, and choose Authenticate.
When Connect RankReactorAI opens, paste the project key and choose Allow.
Ask Claude to use RankReactor, for example “Which site is this RankReactor connection using?”

If you prefer the header method Claude Code documents for static tokens, pass the project key at add time instead of using the browser sign-in:

claude mcp add --transport http rankreactor https://www.rankreactor.ai/mcp --header "Authorization: Bearer <your-project-key>"

The same HTTP shape in .mcp.json (project scope) looks like this. Claude Code also accepts streamable-http as an alias for type: http.

{
  "mcpServers": {
    "rankreactor": {
      "type": "http",
      "url": "https://www.rankreactor.ai/mcp",
      "headers": {
        "Authorization": "Bearer <your-project-key>"
      }
    }
  }
}

Configuration files Claude Code actually reads: ~/.claude.json (local and user scope) and .mcp.json at the project root (project scope). It does not read ~/.claude/mcp.json or %APPDATA%\Claude\mcp.json.

Create a project API key

Sign in and open the project you want the assistant to use.
Open API Key in the dashboard sidebar.
Choose Generate. If a key already exists, choose Regenerate only when you intend to replace it.
Copy the key now. RankReactor shows the full value once.
Paste it on the Connect RankReactorAI page (OAuth) or into the client’s Authorization header.

Available tools

This connection is scoped to one project. Do not ask the assistant to guess another site. Write tools ask for confirmation first.

List projects (list_projects) — List the RankReactor project this API key can use. The key is scoped to exactly one project, so the result is that single site. Example: “Which RankReactor site is this connection using?”
Get reactor status (get_reactor_status) — Read this site's plan, quotas, and recent article or video activity. Example: “How many articles are left on this project today?”
Get metrics (get_metrics) — Read stored search and site health numbers for this RankReactor project. Example: “Show the stored search metrics for this site.”
Refresh metrics (refresh_metrics) — Refresh one stored metric for this project (analytics, technical SEO, website audit, or keywords), subject to that metric's plan limit. Confirmation required. Example: “Refresh analytics for this project if that metric is due.”
List articles (list_articles) — List generated articles for this RankReactor project. Example: “List the generated articles for this site.”
Generate article (generate_article) — Queue an article for this project. Uses the same article limits as the RankReactor dashboard. Confirmation required. Example: “After I confirm, queue an article for the keyword running shoes.”
List UGC videos (list_ugc_videos) — List generated short videos for this RankReactor project. Example: “List UGC videos for this project.”
Generate UGC video (generate_ugc_video) — Queue a short product video for this project. Uses the same monthly video limits as the RankReactor dashboard. Confirmation required. Example: “After I confirm, queue a short product video about our trail runner.”

Troubleshooting

401, invalid, or revoked key — the server returns 401 when no Authorization header is sent, or when the token is invalid or revoked. Generate a key on the matching project and update the client.
Regenerated key — the previous key stops working as soon as you confirm Regenerate. Paste the new key into OAuth consent or the Bearer header.
Revoke — Revoke on the API Key page stops the current key immediately. Existing OAuth and header connections are refused until you generate a new key.
Wrong project or domain — each key belongs to one project. A domain that names a different site is rejected. Create a key on the project you want, or omit the domain so the keyed site is used.
Plan-gated tools — Free can generate its one lifetime article through an assistant; that count is shared with the dashboard. Ongoing article generation needs a paid plan. Refreshing metrics through an assistant needs Starter, Pro, or Ultra. Queuing a UGC video needs Pro or Ultra. Read tools still work on Free.
Article limit — Free has one lifetime article across the dashboard and assistants. Paid plans have a daily article cap (UTC). When a paid daily cap is reached, the tool reports that the article limit has been reached and when it resets.
Video limit — Pro and Ultra have a monthly UGC video cap (UTC). When it is reached, the tool reports that the monthly video limit has been reached.
Metrics cooldown — Starter, Pro, and Ultra can refresh one metric at a time, then wait that metric’s interval. Analytics, technical SEO, and website audit wait 7 days on Starter, 1 day on Pro, and 8 hours on Ultra. Keywords wait 21 / 14 / 7 days. Free does not refresh metrics through the assistant.

Claude-specific notes

Remote connectors on claude.ai and Claude Desktop use OAuth. RankReactor’s consent page asks for the project key — not a Claude login.
Team and Enterprise members cannot add a custom URL themselves. An Owner must add it first.
Claude Code /mcp is the official place to Authenticate, reconnect, or read the error for a 401.
If claude mcp list shows Failed to connect, confirm the URL includes /mcp and that you added the server from the project you are working in (or used --scope user).

Need help?

Email help@rankreactor.ai or reach out on X at @rankreactorai if Claude cannot add the connector or Claude Code stays unauthorized. Include the project domain and which assistant you used.

Questions? Email help@rankreactor.ai or reach out on X at @rankreactorai and include your project domain.