The best SEO MCP server for Codex

Codex runs in a shell and speaks MCP, so it can reach live keyword, traffic, backlink and AI-visibility data instead of guessing at numbers. Point it at omnifamous and the research stops being fiction.

Live now: the MCP server, the free AI visibility audit and the keyword tools. Codex is the odd one out on config: it reads TOML from ~/.codex/config.toml under an [mcp_servers.<name>] table, not the JSON mcpServers block every other client uses.

Setup

Add the SEO MCP server to Codex

Codex is the odd one out on config: it reads TOML from ~/.codex/config.toml under an [mcp_servers.<name>] table, not the JSON mcpServers block every other client uses.

Fastest: let Codex do it

Paste this in and it reads our skill, then writes its own config in the format Codex expects.

Read https://omnifamous.com/mcp/skill.md and set up the OMNIFAMOUS SEO MCP server for this project, then use it to audit my site's search and AI visibility.

Command line (recommended)

  1. Run the commands below in your terminal
  2. Sign in to OMNIFAMOUS in the browser, pick a workspace and choose Editor or Viewer access
  3. Run /mcp inside Codex to confirm the tools loaded
codex mcp add omnifamous --url https://mcp.omnifamous.com
codex mcp login omnifamous

With an API key

  1. For CI or headless runs, read a workspace key from the environment
  2. Run /mcp inside Codex to confirm the tools loaded
export OMNIFAMOUS_API_KEY="sk_your_workspace_key"
codex mcp add omnifamous \
  --url https://mcp.omnifamous.com \
  --bearer-token-env-var OMNIFAMOUS_API_KEY

Codex stores servers as TOML in ~/.codex/config.toml under [mcp_servers.omnifamous] with url = the server URL. With a key, keep OMNIFAMOUS_API_KEY out of your shell history file.

What you get

Connecting omnifamous to Codex

Every surface of the engine, as tools your agent can call mid-conversation.

MCP server

Live now

One `codex mcp add --url` command, then `codex mcp login` to sign in. Codex gets the full tool catalog: keyword ideas, traffic estimates, backlinks, competitor gaps, page checks and AI visibility.

AI visibility tools

Live now

Check whether ChatGPT, Claude, Gemini and Perplexity mention a brand on a sample of questions, and read your saved AI Visibility monitoring results: answers, cited domains and trend.

Free audit and keyword tools

Live now

Anonymous AI visibility audit and keyword research at /tools/seo-audit, no login required.

Public API

Live now

The page-check and speed-audit tools also have plain HTTP endpoints, so you can script them without an MCP client. Keyword, traffic, backlink and gap data is MCP only.

What we do for you

We do the SEO work, not hand you another dashboard

Whichever way you connect, the omnifamous engine does the heavy lifting for your brand.

Audits your AI visibility so you can see which prompts name your brand and which name a competitor.

Researches winnable keywords for your market with real search data behind every pick.

Compares your keywords and backlinks against a competitor so you know what to write next.

With the AI Visibility plan, reads your scheduled monitoring results so you can prove the trend as content ships.

How it works

From Codex to ranking content

Four steps. You stay the editor, the engine handles the rest.

1

Add the server to Codex. One `codex mcp add --url` command, then `codex mcp login` to sign in.

2

Ask in plain language. The agent picks the tools, so you never call one by hand.

3

Review the research. Every number comes from a live data provider, not from the model.

4

Decide what to ship. You stay the editor while the tools supply the numbers.

FAQ

Questions, answered

Everything you need to know about how the engine does the work for you.

Yes. One `codex mcp add --url` command, then `codex mcp login` to sign in. Once it is connected, Codex can research keywords, estimate traffic, check backlinks, compare keyword gaps against a competitor, inspect pages, and check whether ChatGPT, Claude, Gemini and Perplexity mention your brand.

Codex is the odd one out on config: it reads TOML from ~/.codex/config.toml under an [mcp_servers.<name>] table, not the JSON mcpServers block every other client uses. The exact config block for Codex is on this page, ready to copy.

Because Codex stores all its settings in config.toml. The keys map one to one onto the JSON other clients use: mcp_servers becomes mcpServers, http_headers becomes headers. The block on this page is already in the right format.

Yes. Codex has a shell, so a cron job or CI step can run it against the MCP server with your workspace key. Paid tools need an Editor key and draw from the workspace credit balance.

Because it will make the numbers up. Language models routinely invent search volumes, difficulty scores and competitor rankings that look plausible and are wrong. Every number our tools return comes from a live data provider or your own workspace.

Page inspection and robots/sitemap checks are free without a key, broken-link checks are free with a key, and reads of your saved AI-visibility data cost no credits (they need the AI Visibility plan). Tools that buy live market data spend workspace credits at a published per-call price, charged only on a successful answer. There is no signup credit grant.

Two ways. On demand, ai_visibility_run_scan asks ChatGPT, Claude, Gemini and Perplexity three questions about your domain and reports whether your brand appears. For tracking, the AI Visibility plan scans your own prompts on a schedule, and the workspace read tools return those saved answers, cited domains and trends to your agent.

Still have questions? Talk to us

More agent runtimes

Run omnifamous from the tools you already use

Same engine, wherever your agent lives. See how it connects to each runtime.

Stop letting Codex guess at SEO

Connect the server and it works from real keyword, SERP, backlink and AI-visibility data instead of numbers it invented. Start with the free audit, no account and no card.

Run my free auditNo credit card required. Results in under 5 minutes.