MCP Guide · Free · Read-only

Connect Codex to SEOMentor

Codex connects to remote MCP servers straight from its own CLI. Two commands and an OAuth approval, and it can read your real SEOMentor data alongside whatever repository you're working in.

Before you start

A SEOMentor account with at least one completed scan
The Codex CLI installed and signed in

Connect in 3 steps

Add the server

Run this from your terminal. It registers SEOMentor as a remote MCP server for Codex.

codex mcp add seomentor --url https://www.seomentor.io/mcp

This opens your browser to SEOMentor's sign-in and consent screen.

codex mcp login seomentor

Verify the connection

Confirm SEOMentor shows up and is authenticated before relying on it.

codex mcp list

Try it once connected

Ask these, word for word or close to it. Codex calls SEOMentor's MCP tools behind the scenes and answers using your real account data.

You ask:

“List my SEOMentor sites and their current scores.”

Example of what comes back:

Codex calls list_sites and prints each hostname, its SEO score, and whether Search Console/GA4 are connected for it.

You ask:

“Pull the latest scan for [yoursite.com] and tell me the top 3 things to fix.”

Example of what comes back:

It calls get_scan_results, reads through the technical, speed, and content sections, and ranks the issues by estimated impact before listing the top 3.

You ask:

“Which queries in Search Console lost the most clicks in the last 28 days?”

Example of what comes back:

It calls get_gsc_performance and sorts by click change, surfacing the biggest drops first, useful for catching a ranking slip early.

What Codex can and can't do

Every tool on SEOMentor's MCP server is read-only. Codex can pull your scan results, Search Console and Analytics data, and score history, but it can't start a new scan, change a setting, or touch billing. The connection uses OAuth, so you approve it once on a consent screen and can revoke it anytime from SEOMentor settings or from Codex itself.

Troubleshooting

codex mcp login opens nothing / times out

This is common over SSH or in a container with no browser to redirect to. Codex has a remote-host flow for this case: a one-time code you complete via curl instead of a browser redirect. Check codex mcp login --help for the exact syntax.

codex mcp list doesn't show seomentor as authenticated

Re-run the login command. The add step only registers the server, it doesn't authenticate on its own.

Config added via CLI isn't showing up in another terminal/session

Check whether it was added at user level (~/.codex/config.toml, available everywhere) or project level (.codex/config.toml, only in that project). This depends on which directory you ran the add command from.

Disconnect anytime

•Run codex mcp remove seomentor from your terminal.
•Or in SEOMentor: Settings → Connected Apps → revoke Codex's access.

Frequently Asked Questions

Can I use this non-interactively, e.g. in a script?

Yes. Once authenticated, Codex's non-interactive execution mode (codex exec) can call SEOMentor's tools the same as an interactive session, useful for scheduled reports or CI checks.

Does this need approval for every tool call?

Depends on your Codex approval-mode setting. You can require a prompt per call, or trust the server once connected. Since every SEOMentor tool is read-only, most people set it to not prompt for these.

Is the config.toml entry sensitive?

No, it's just the server URL. The actual OAuth token from login lives in Codex's own credential storage, not in the config file.

No SEOMentor account yet?

Get started free