ContextBolt SEO in Gemini CLI (2026 Setup Guide)

Gemini CLI is Google’s open-source, terminal-based AI agent. It speaks the Model Context Protocol, so you can wire in ContextBolt SEO and pull live keyword, SERP, domain, and competitor data straight into your terminal workflow.

Gemini CLI has file access, so every lookup you run gets mirrored to a ./seo-findings/ folder in your project as markdown. Your research lives next to your code, searchable and version-controlled, instead of disappearing into the session.

SEO research where you ship

When you are building, the question “what should this rank for, and who already owns it?” is one you want answered without breaking flow. With ContextBolt SEO in Gemini CLI you ask it in the terminal and the numbers come back inline. No dashboard, no export, no second tool.

Because these are MCP tools, Gemini CLI chains them. “Find ten low-difficulty keywords for my docs site, check which ones a competitor already ranks for, and list the gaps” is one prompt, not ten dashboard sessions, and the whole session is written to disk.

The config entry

Add ContextBolt SEO to ~/.gemini/settings.json (global) or .gemini/settings.json (per project), under the mcpServers object:

{
  "mcpServers": {
    "contextbolt-seo": {
      "httpUrl": "https://seo.contextbolt.app/mcp/YOUR_TOKEN"
    }
  }
}

Note the key is httpUrl, not url. Gemini CLI uses httpUrl for a remote streamable-HTTP server, reserves url for SSE endpoints, and uses command plus args for local stdio servers. This is the one detail that trips people up, since Cursor and Codex use url and Windsurf and Antigravity use serverUrl. Save the file, start Gemini CLI, and run /mcp to confirm the server and its SEO tools loaded. Your URL contains a personal token, so keep settings.json out of public repos or pull the URL from an environment variable. The full tour of tools and workflows is in the ContextBolt SEO guide.

How to connect ContextBolt SEO to Gemini CLI

1. Subscribe and get your MCP URL

   Subscribe to ContextBolt SEO ($35/month for 1,000 lookups). Your private MCP URL arrives by email and looks like https://seo.contextbolt.app/mcp/YOUR_TOKEN. Keep it private, like a password.

2. Add it to ~/.gemini/settings.json

   Open ~/.gemini/settings.json for a global setup, or .gemini/settings.json in your repo root for a per-project one. Under the mcpServers object, add contextbolt-seo with an httpUrl field pointing at your MCP URL. Gemini CLI uses httpUrl for a remote HTTP server, not url.

3. Run /mcp to confirm the tools loaded

   Save the file, start Gemini CLI, and run /mcp. It lists every connected server and the tools each one exposes, so you can confirm contextbolt-seo is live and its SEO tools loaded before you rely on them.

4. Connect your Search Console (optional, free)

   Ask 'connect my Google Search Console', approve read-only access on Google's consent screen, and Gemini CLI can read your real clicks, positions, and quick wins. The Search Console tools are free and never spend your monthly lookups.

Example prompts for ContextBolt SEO + Gemini CLI

Once connected, try asking Gemini CLI:

What you can do with ContextBolt SEO in Gemini CLI