RankReactorAI
LoginSign Up
Docs

Documentation

RankReactor Gemini CLI

Add the RankReactor SEO MCP server to Gemini CLI in settings.json using httpUrl and an Authorization header, or OAuth discovery.

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.

Gemini CLI reads MCP servers from the mcpServers object in settings.json. Official docs require one of command, url, or httpUrl. RankReactor is a Streamable HTTP server, so use httpUrl (precedence is httpUrl, then url, then command). The endpoint is https://www.rankreactor.ai/mcp.

settings.json location

  • User: ~/.gemini/settings.json — every Gemini CLI session for your account.
  • Project: .gemini/settings.json in the project root — overrides user settings for that project.
  • There is also a system-wide file for administrators. You do not need it for a personal RankReactor connection.

Streamable HTTP with a Bearer header

Gemini CLI documents a headers object on url or httpUrl entries. Send the project key as Authorization: Bearer ….

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

OAuth discovery

Gemini CLI also documents OAuth for remote MCP servers. You can omit header and OAuth fields and let the CLI discover authentication from a 401 and the server metadata. That requires a local browser for the redirect.

{
  "mcpServers": {
    "rankreactor": {
      "httpUrl": "https://www.rankreactor.ai/mcp"
    }
  }
}
  1. Save settings.json.
  2. Start Gemini CLI in a directory that can see that file.
  3. If the server needs sign-in, run /mcp auth rankreactor (or /mcp auth and pick the server).
  4. When Connect RankReactorAI opens, paste the project key from Dashboard → API Key and choose Allow.
  5. Ask Gemini to list the RankReactor project or stored metrics.

Official Gemini CLI docs store OAuth tokens under ~/.gemini/ after a successful browser flow. Headless or remote sessions without a browser should use the Authorization header instead.

Create a project API key

  1. Sign in and open the project you want the assistant to use.
  2. Open API Key in the dashboard sidebar.
  3. Choose Generate. If a key already exists, choose Regenerate only when you intend to replace it.
  4. Copy the key now. RankReactor shows the full value once.
  5. 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.

Gemini CLI-specific notes

  • url is the SSE field; httpUrl is Streamable HTTP. RankReactor is hosted as Streamable HTTP — prefer httpUrl.
  • If two MCP servers expose the same tool name, Gemini CLI prefixes tools with the server alias (rankreactor__list_projects). Name the server rankreactor so prompts stay readable.
  • excludeTools wins over includeTools on the same server.
  • Do not put the project key in a committed .gemini/settings.json. Use the user file or the client’s own secret prompt.

Need help?

Email help@rankreactor.ai or reach out on X at @rankreactorai if Gemini CLI cannot list RankReactor tools. Include the project domain and which assistant you used.

PreviousWindsurfNextGrok Bot

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