Your developers already use Codex to ship code. The SEO question is what that agent can see while it edits a client’s site: rankings, Search Console data, audit findings, AI visibility.
The best Codex MCPs for SEO connect OpenAI’s coding agent to Rankability, Ahrefs, Semrush, Search Console, and crawlers. Most return raw SEO data, and someone still has to turn it into a fix or a client deliverable. Rankability is the exception: one connection covers every client workspace and goes from research to a reviewed fix or delivered draft.
This guide compares eight options on multi-client support, AI search coverage, cost, setup effort, and whether the vendor documents setup for it at all. You will know which connector should be your hub and which ones to plug in beside it.
Start with the quick picks, then jump to the tool that fits your workflow.
Quick Picks: Codex MCPs for SEO Compared
| # | Tool | Best for | Standout capability | Reads data or takes actions | Codex setup |
|---|---|---|---|---|---|
| 1 | Rankability | SEO and AEO agencies running many clients | Client workspaces plus research-to-draft workflow | Both, with approval | Official guide (remote, OAuth) |
| 2 | Ahrefs MCP | Backlink and competitor research | Ahrefs index next to your code | Reads | Generic remote server |
| 3 | Semrush MCP | Teams already on Semrush | Semrush keyword and competitor data | Reads | Generic remote server |
| 4 | DataForSEO MCP | Custom SEO agents and pay-as-you-go data | Official Codex plugin | Reads | Official plugin |
| 5 | SE Ranking MCP | Broad SEO and GEO tool coverage | 180+ SEO and GEO tools, hosted | Reads | Official guide (remote) |
| 6 | Google Search Console MCP | Free first-party performance data | Search analytics, URL inspection, sitemaps | Reads, optional writes | Community guide (stdio) |
| 7 | Google Analytics MCP | Traffic and conversion context | GA4 reports, funnels, realtime | Reads | Generic stdio server |
| 8 | Firecrawl MCP | Crawling and page extraction | Scrape, map, and crawl any site | Reads | Generic remote or stdio |
What Is a Codex MCP and How Does It Connect?
Model Context Protocol (MCP) is an open-source standard for connecting AI applications to external systems. An SEO MCP server exposes tools the agent can call, limited to the permissions you grant. The Codex CLI, the IDE extension, and the ChatGPT desktop app all support MCP servers and share one configuration, so a server you add once works in each.
The configuration lives in ~/.codex/config.toml. You can also scope servers to one project with .codex/config.toml, loaded only for trusted projects. Each server gets its own [mcp_servers.<name>] table, over one of two transports:
- Streamable HTTP (remote servers): set a
url. OAuth is the default, and you can usebearer_token_env_varto read an API key from an environment variable instead of writing it in the file. - Stdio MCP server (local): set a
commandandargs, such as annpx,uvx, orpipxlauncher, withenvorenv_varsfor credentials.
From the terminal, codex mcp add registers a server (use --url for remote servers), codex mcp login <name> completes an OAuth sign-in, and codex mcp list shows what is configured. Inside a session, /mcp shows which servers are active.
Two settings matter most for agencies. default_tools_approval_mode controls whether the agent asks before calling a server’s tools (auto, prompt, writes, or approve), and enabled_tools or disabled_tools lets you limit a server to the tools a task actually needs.
Also separate a data MCP (keyword volume, backlinks, SERPs, rankings, clicks) from a workflow MCP, which builds the brief, writes the draft, and prepares it for publishing. Most SEO MCP servers are data MCPs.
Why Codex Is Different: SEO Work Inside the Client’s Code
Most SEO MCP guides assume a chat assistant. Codex is a coding agent that works inside a repository, which changes what an SEO MCP is for.
With live data connected, the agent can read a client’s site code and search data in the same session, then turn findings into reviewed code changes:
- Structured data: add or fix a JSON-LD block in the template that renders a page type.
- Indexing signals: correct canonical tags, robots directives, hreflang, and sitemaps flagged in an SEO audit.
- On-page fixes: titles, meta descriptions, heading structure, and image alt text on pages losing clicks in Search Console.
- Internal linking: add links to pages with few inbound links, based on crawl data.
- Crawl errors: fix broken links, redirect chains, and the crawl errors a crawler or Bing Webmaster Tools reports.
Every change arrives as a diff your developer reviews. Per-project configuration means each client repository can carry its own servers and approval rules.
If your team works mainly in chat, our guide to the best Claude MCPs for SEO covers that side.
How We Evaluated Codex MCPs for Agencies
This comparison uses published product documentation and pricing pages, checked in November 2026, not hands-on benchmark testing. Rankability publishes this article and ranks its own product first for agencies; the reasons are laid out below alongside the specialist tools we would add next to it.
We weighed seven criteria:
- Multi-client support: Can one connection work across every client, with the correct workspace, brand rules, and exclusions?
- Actions: Does it only retrieve data, or can it create deliverables with approval?
- AI search coverage: How many AI engines does it track, and does it separate brand mentions from citations?
- Freshness: Live Google results, scheduled snapshots, or estimates?
- Cost model: Suite subscription, monthly API unit quota, per-call credits, or free?
- Setup effort: Hosted sign-in, or local software and credentials your team must maintain?
- Codex documentation: Does the vendor publish Codex-specific setup, or do you connect it as a generic remote or stdio server?
As of November 2026, Rankability, DataForSEO, and SE Ranking publish official Codex setup paths, and the community mcp-gsc project documents a CLI config. The others work through standard remote or stdio patterns, following OpenAI’s documentation rather than the vendor’s.
1. Rankability: Best Overall for SEO and AEO Agencies
Rankability leads this list because it is built around client workspaces. One MCP connection works across every client while applying each client’s brand voice, knowledge base, and exclusions. One client’s rules never leak into another client’s work.
Key Features
- Keyword research and SERP analysis: Researcher returns search volume, keyword difficulty, CPC, intent, and the pages that rank in live Google results.
- SERP-driven briefs and drafts: Copywriter builds briefs from SERP and AI-answer research, then writes drafts in the client’s voice.
- Page optimization and site audits: score existing pages against a target keyword, find content gaps, review technical findings from the site audit crawler, and verify fixes after a recrawl.
- AI visibility tracker: Tracker runs daily checks across 11 AI platforms, including ChatGPT, Google AI Overviews, Google AI Mode, Claude, Perplexity, Gemini, and Microsoft Copilot, with mentions, citations, and competitor comparisons.
- Google Search Console performance: clicks, impressions, CTR, and position per client at query or page level, with period comparisons.
- Backlinks and client reporting: link data and client-ready analyses.
- Documented Codex setup: the Rankability MCP guide covers the Codex desktop app and IDE extension, with OAuth as the preferred sign-in.
Agency Workflow: Live Data to Code Fix to Draft
Open a client’s site repository and ask the agent to pull the pages that lost the most Search Console clicks this month, along with the related site audit findings from Rankability. It can then open the templates behind those pages and propose title, meta description, and schema fixes as a diff for your developer to review.
For pages that need new content rather than a code fix, the same session can create a brief, write a refreshed draft after you approve the brief, and deliver it as a draft to the client’s WordPress site (Webflow, GitHub, and webhooks are also supported). Rankability delivers drafts; a person approves and publishes.
Pricing, Limits, and Who It’s For
Pricing: Starter is $97/month, Agency is $297/month, and Agency Pro is $497/month. Every tier includes MCP and API access. A 7-day free trial is available; a card is required.
Best for: Agencies and in-house teams managing multiple sites and repeatable deliverables.
Limits: Draft delivery requires a connected CMS integration. Campaigns that depend on the deepest backlink index may still need a specialist dataset such as Ahrefs.
Agency verdict: Choose Rankability when your main requirement is running client work, not just retrieving data. It acts as the hub, and specialist MCPs plug in beside it.
2. Ahrefs MCP: Best for Backlink and Competitor Data
Ahrefs fits when a strategy depends on backlinks or competing pages. Its official remote MCP server runs at https://api.ahrefs.com/mcp/mcp over Streamable HTTP. When you connect, Ahrefs shows a consent screen and creates a dedicated API key tagged with MCP scope.
What it does well:
- Backlink profiles and domain rating from the Ahrefs index.
- Keyword data: search volume, traffic potential, and keyword difficulty.
- Content gap and competitive analysis across competing SERPs.
Pricing: MCP is available on Lite, Standard, Advanced, and Enterprise, and usage draws from the same monthly API units as direct API calls. Per the Ahrefs API page, Lite is $129/month, Standard is $249/month, Advanced is $449/month, and Enterprise is $1,499/month.
Best for: Analysts who want link data next to the code they change.
Limits: Ahrefs publishes setup guides for Claude, Claude Code, ChatGPT, and other clients, but not Codex, so you connect it as a generic remote server. Ahrefs also states that using the endpoint from custom scripts or bridges is not permitted; use it interactively and use the API for automation. Monthly API units cap research scope.
Agency verdict: Add Ahrefs beside your workflow tool when a campaign needs deep link intelligence. Our Ahrefs review covers the platform and per-seat costs.
3. Semrush MCP: Best for Teams Already on Semrush
Semrush makes sense when an agency already lives in its platform. The Semrush MCP runs at https://mcp.semrush.com/v2/mcp, uses Streamable HTTP only, and signs in with OAuth by default. Agents without OAuth support can send an API key in an Authorization: Apikey header.
What it does well:
- Semrush SEO API data, including domain, organic competitor, and backlink analysis.
- Read-only access to existing Projects data.
- Traffic and market data through the Trends API, where the account has access.
Pricing: No separate MCP fee. Semrush One Starter, Semrush One Pro+, SEO Classic Pro, and SEO Classic Guru include 50,000 API units that refresh at renewal. SEO Classic Business and Semrush One Advanced need an API units package, and any Trends API plan includes MCP access.
Best for: Agencies that already rely on Semrush.
Limits: Semrush documents setup for Claude, Claude Code, ChatGPT, Cursor, VS Code, and others, but not Codex. Add it as a remote server with codex mcp add and --url, then sign in with codex mcp login. Account entitlements and API units limit what it can retrieve.
Agency verdict: Do not switch suites for a connector. If you already pay for Semrush, connect it and keep location, device, and date range consistent. See our Semrush review for the full picture.
4. DataForSEO MCP: Best for Pay-As-You-Go Data and an Official Codex Plugin
DataForSEO supplies data behind many SEO tools and is the only vendor on this list with an official Codex plugin. From the terminal in the ChatGPT desktop app, run codex plugin marketplace add dataforseo/codex-plugins, add the plugin under Plugins, and approve a browser sign-in. There are no API logins or passwords to paste.
What it does well:
- SERP data across Google, Bing, and other engines.
- Keyword volume, CPC, competition, and trends.
- Competitor and market research through DataForSEO Labs.
- Backlinks, on-page audits, and LLM and GEO analysis.
Pricing: Pay-as-you-go, with no monthly subscription. You pay for the data you request, at the same rates as the direct API.
Best for: Technical agencies building their own research agents or reporting systems.
Limits: Your team owns orchestration and interpretation. Outside the plugin, the remote MCP server at https://mcp.dataforseo.com/v3/mcp uses Basic Auth, and local options run through npx -y dataforseo-mcp-server or Docker with your API credentials in environment variables.
Agency verdict: Choose DataForSEO when flexibility and per-call pricing matter more than a ready-made client workflow. Set spending limits before broad discovery runs. If rankings are your main need, compare it in our best rank tracking APIs guide.
5. SE Ranking MCP: Best for Broad SEO and GEO Coverage
SE Ranking combines rank tracking, audits, and research, and publishes Codex setup instructions. Run codex mcp add se-ranking --url https://api.seranking.com/mcp, then sign in with your SE Ranking account through OAuth. Headless environments can send an API key in the X-Api-Key header instead.
What it does well:
- More than 180 SEO and GEO tools in one hosted connection.
- Keyword research, domain and competitor analysis, and backlinks.
- Website audits plus rank tracking tied to your projects.
- AI search visibility data alongside classic SEO metrics.
Pricing: MCP access is included in every SE Ranking subscription and runs on your plan’s API credits. A pay-as-you-go API plan starts at $50 for 250K credits if you want MCP without a full subscription, and the free trial includes 100K credits with no card.
Best for: SEO leads who want rank tracking and broad research in one hosted connection.
Limits: Credits matter for large competitor investigations and recurring multi-client reporting. Sub-accounts cannot use the sign-in flow and need an API key from the account administrator.
Agency verdict: A sensible pick for weekly ranking checks. Estimate tool calls against your credits before rolling it out across clients. Our SE Ranking review covers the platform.
6. Google Search Console MCP: Best Free First-Party Performance Data
Search Console is the only first-party source of Google clicks and impressions. The open-source mcp-gsc server is MIT-licensed, maintained by the community rather than Google, and its README includes a Codex CLI configuration for ~/.codex/config.toml.
What it does well:
- Search analytics on clicks, impressions, CTR, and position, with filters by country, device, query, or page.
- Period comparisons that surface declining pages and keyword cannibalization.
- Batch URL inspection for up to 10 URLs, plus indexing checks.
- Sitemap listing, error reporting, and submission. Destructive tools stay off unless you set
GSC_ALLOW_DESTRUCTIVEto"true".
Pricing: Free. You supply your own Google credentials.
Best for: Teams that want first-party data next to the code at no cost.
Limits: It runs locally through uvx with OAuth or a service account, so each developer maintains their own setup and property access. Rankability already includes per-client Search Console data if you would rather not.
Agency verdict: A strong free addition for technical teams. Confirm each client property is authorized before running cross-client analysis.
7. Google Analytics MCP: Best for Traffic and Conversion Context
The Google Analytics MCP server is published under the googleanalytics GitHub organization and labeled experimental. It adds what Search Console cannot: what visitors did after they arrived.
What it does well:
- Core reports, funnel reports, and custom dimensions and metrics.
- Realtime reports, so you can confirm whether a traffic drop is still happening.
- Read-only by default; the single write tool (property annotations) needs an
--allow-writeflag.
Pricing: Free. You need a Google Cloud project with the Analytics APIs enabled.
Best for: Connecting ranking and click changes to sessions and conversions.
Limits: The README names Gemini CLI, Gemini Code Assist, and Claude Code, not Codex, so you add it as a stdio server that runs pipx run analytics-mcp. Authentication uses gcloud Application Default Credentials.
Agency verdict: Add it when clients ask whether SEO work produced business results, not just clicks.
8. Firecrawl MCP: Best for Crawling and Page Extraction
The Firecrawl MCP retrieves page content for the agent to analyze. Useful for competitor teardowns and content inventories before a migration.
What it does well:
- Scrapes pages to Markdown or JSON and parses PDFs.
- Maps every URL on a site and crawls sections of it.
- A hosted endpoint at
https://mcp.firecrawl.dev/v2/mcp, or a local server throughnpx -y firecrawl-mcp.
Pricing: Credit-based. A keyless hosted tier offers rate-limited scrape, search, and parse; crawl and map need an API key. Check Firecrawl’s current plans before heavy use.
Best for: On-page and competitor content analysis.
Limits: The README has no Codex section, so you connect it as a generic remote server with your key in bearer_token_env_var, never in the URL. Extracted text is not keyword volume, rankings, or backlink data.
Agency verdict: A practical utility for content audits and migrations. Cap crawl sizes so one request does not drain your credits.
More SEO MCP Servers That Work With Codex
The eight picks cover most agency work. These servers fill specific gaps. Several of them change the site rather than return SEO data, so it helps to split them into data servers (read SEO data) and site servers (crawl, edit, or configure the site itself).
Crawlers and Site Audit Tools
- Screaming Frog SEO Spider MCP: official in SEO Spider version 24 and a paid licence feature only. It can start, pause, and resume crawls, generate reports and bulk exports, and return URL content, links, and screenshots. Node.js tools are off by default, and file access is limited to an allowed base directory. Screaming Frog documents Claude Desktop (stdio) and LM Studio (Streamable HTTP from the running Spider), not Codex. Codex can reach a Streamable HTTP server by URL, so the likely route is a remote entry pointing at the local URL the Spider shows, but Screaming Frog has not documented it.
- Sitebulb MCP: an official remote server at
https://mcp.sitebulb.com/cloudorhttps://mcp.sitebulb.com/desktop. It signs in with OAuth only (no API-key path), is read-only, and offers 15 tools that work from finished audits, returning up to 50 sample URLs per hint. Sitebulb names Codex among clients that should work but has not verified it. - Chrome DevTools MCP: an Apache-2.0 server from the ChromeDevTools project that records performance traces and inspects network requests and console messages in a live Chrome browser. Useful for debugging page speed and INP problems before Core Web Vitals work. Its README has no Codex section.
Search Engine Data
- ahonn/mcp-server-gsc: an MIT-licensed alternative Search Console server run with
npx -y mcp-server-gsc. It authenticates with a Google Cloud service account (GOOGLE_APPLICATION_CREDENTIALS) and itssearch_analyticstool returns up to 25,000 rows with regex filters and quick-wins detection. - Bing Webmaster Tools: the community isiahw1/mcp-server-bing-webmaster server (MIT) reads a
BING_WEBMASTER_API_KEYand covers URL submission, query and page stats, crawl errors and crawl settings, sitemaps, and link analysis.
WordPress SEO Plugins (Site Servers)
- AIOSEO MCP: official, added in AIOSEO 4.9.8 on WordPress 6.9 or later. It exposes AIOSEO features through the WordPress Abilities API (28 abilities at launch) and is free on every plan, Lite included, though some abilities need Pro or Elite.
- Rank Math MCP: published by Rank Math as an OAuth server at
your-site/wp-json/mcp/mcp-oauth-server. Agents can read SEO titles, meta descriptions, focus keywords, robots and canonical settings, schema, redirections, robots.txt, and llms.txt, and can change homepage SEO and global settings. Rank Math names Claude Desktop, ChatGPT, and GitHub Copilot. - Yoast SEO and SEOPress: we found no official MCP server from either. Third-party WordPress plugins bridge their SEO fields; review what they can write before connecting a client site.
AI Visibility and Market Data
- Peec AI and Profound: both offer hosted MCP servers for AI visibility data. Worth a look if you already use either platform; see our Peec AI review and Profound AI review. Rankability includes AI visibility tracking alongside the rest of the agency workflow.
- Similarweb MCP: market and traffic research. Useful for competitive sizing rather than day-to-day client SEO work.
- Community wrappers such as cnych/seo-mcp: unofficial. Review security and authentication before connecting client accounts.
How to Set Up an MCP in Codex
Start with one client repository and one read-only question.
- Pick the scope. Use
~/.codex/config.tomlfor servers you want everywhere, or a project’s.codex/config.tomlfor a single client repository (trusted projects only). - Add the server. For a remote server, run
codex mcp add <name> --url <server-url>. For a local server, runcodex mcp add <name> -- <command>. Or edit the TOML directly. - Authenticate. Run
codex mcp login <name>for OAuth servers. For API keys, setbearer_token_env_varand export the key in your shell. - Check it. Run
codex mcp list, then type/mcpin a session to confirm the server is active. - Limit and test. Set
default_tools_approval_modeand, where useful,enabled_tools. Ask for a dated, read-only summary first, and have the agent label confirmed data separately from its interpretation.
Keep credentials out of prompts, AGENTS.md, and any config file you commit. An OAuth client_secret is stored in config.toml as plain text, so keep that file private.
Example config.toml
[mcp_servers.rankability]
url = "https://app.rankability.com/mcp"
auth = "oauth"
default_tools_approval_mode = "writes"
[mcp_servers.se-ranking]
url = "https://api.seranking.com/mcp"This configuration asks before Rankability runs any write tool. For the full walkthrough, see the Rankability MCP setup guide and OpenAI’s Codex MCP documentation.
Turn Your SEO Checklist Into a Codex Agent Skill
Codex Agent Skills package repeatable instructions. A skill is a folder with a SKILL.md file (a name, a description, and instructions) plus optional scripts and references. Codex reads each skill’s name and description at startup and loads the full instructions only when a task needs them. Skills work in the Codex CLI, the IDE extension, and the Codex app, and plugins can bundle them.
For an agency, a technical SEO audit skill is the obvious first one. Write down your own checks (SEO title and meta description length, schema type per template, canonical and robots rules, hreflang, image alt text, internal linking, llms.txt) and which MCP tools to call for each. Every client repository then gets the same SEO checks, run the same way. Keep API keys and client data out of skill files.
Example Rankability Agency Prompts for Codex
- “For client X, list the 20 pages that lost the most Search Console clicks versus last month. Open the templates that render them in this repo and propose title and meta description fixes as a diff.”
- “Pull the latest Rankability site audit for client X and fix the canonical, hreflang, and structured data issues in this codebase. Show me the diff before changing anything.”
- “For client X, show AI visibility gaps against competitors Y and Z. Separate mentions from citations and recommend three topics to cover.”
- “Research keyword Y for client X and create a brief using this workspace’s brand voice and exclusions. Wait for my approval before writing the draft.”
- “Write the approved draft for client X and deliver it to WordPress as a draft. Do not publish.”
FAQ
What Is the Best Codex MCP for SEO Agencies?
Rankability, because one connection covers every client workspace: research, briefs and drafts, optimization, reporting, Search Console data, and AI visibility. DataForSEO suits pay-as-you-go data, and SE Ranking suits broad SEO and GEO coverage.
Does Codex Support MCP Servers?
Yes. The Codex CLI, the IDE extension, and the ChatGPT desktop app support MCP servers and share one configuration. It connects to local servers over stdio and to remote servers over Streamable HTTP, with OAuth or bearer tokens.
Which SEO MCPs Have Official Codex Setup Instructions?
Rankability, DataForSEO (as a Codex plugin), and SE Ranking publish official Codex setup paths, and the community mcp-gsc project documents a CLI config. Sitebulb lists Codex as a client that should work. Ahrefs, Semrush, Google Analytics, Firecrawl, and Screaming Frog work through generic remote or stdio setup.
Can Codex Make SEO Changes to a Client Website?
Yes, in a trusted repository: metadata, structured data, redirects, sitemaps, and internal linking. On WordPress, site servers such as AIOSEO MCP and Rank Math MCP can change SEO settings directly. Use narrow tool permissions, require approval for writes, review every diff, and follow the client’s deployment process.
How Much Do SEO MCPs for Codex Cost?
It varies. Search Console and Google Analytics servers are free, Rankability starts at $97/month, Ahrefs API plans start at $129/month, SE Ranking’s pay-as-you-go API starts at $50 for 250K credits, and DataForSEO charges per request. API units and crawl credits add variable costs.
Bottom Line: Which Codex MCP Should Your Agency Use?
If you run SEO for many clients, start with Rankability as the hub: one connection, every client’s context, and a workflow that ends in a reviewed code fix or a delivered draft. Add Ahrefs, Semrush, DataForSEO, or SE Ranking when a specific dataset justifies the cost, and use the free Search Console and Analytics servers for raw first-party data.
Connect Rankability to Codex, open one client repository, and run a read-only Search Console review. Then start a 7-day free trial and take one page from a lost-clicks report to a reviewed fix.