mttr for Codex

Let Codex fix your SEO

Four lines in Codex’s config. Then Codex reads the fixes worth the most, works through them in your code, and mttr checks each one.

  1. Readmttr_briefmttr reads the site and hands over the fixes worth the most, each with its pages.
  2. Fixthe agentThe agent makes each change in your repository, the way it would any task.
  3. Checkmttr_rescanmttr reads the site again and says what each change fixed, and anything it broke.
~/.codex/config.toml
[mcp_servers.mttr]
url = "https://mttr.si/mcp"
bearer_token_env_var = "MTTR_KEY"

A real site, fixed by its agent

Every read here was one its agent asked for, and mttr checked each one.

Site t7txivpr climbed from 81 to 94 in 2 hours4 reads its agent asked for, each checked by mttr, Oct 17
Real site
Score
94+13 vs 81
Place
#336up 7,658 of 23,659
Rules passing
38 of 40+8 vs 30
Score, read by readIts agent askedBefore
7085100 +11, 3 fixes proved 4:27 pm8:56 pm
Fixes mttr provedPages each was failing on
  • Add a way to get in touch
    94
  • Put figures in tables
    38
  • Answer the first question right under it
    37
  • Phrase headings as questions
    37
  • Fix title lengths
    31
A real site, shown by its code: who owns it is theirs to tell. A score says pages are well formed, not that an assistant cites the site.

Connect Codex in a minute

A free key and one setting. Your agent does the rest.

Answeringhttps://mttr.si/mcp62 toolsStreamable HTTP

  1. 1
    Get a key

    Free, with an email. It reads any site's public report; claim your own site to add its private parts.

    Or connect with no key, and your agent signs you up itself with mttr_signup.
  2. 2
    Connect Codex

    First put the key in your shell, where no file you commit can hold it.

    Terminal
    export MTTR_KEY=mk_your_key

    Add this to Codex’s settings. It reads the key from your shell when it starts.

    ~/.codex/config.toml
    [mcp_servers.mttr]
    url = "https://mttr.si/mcp"
    bearer_token_env_var = "MTTR_KEY"
  3. 3
    Ask Codex something

    In words. It picks the call, and the answer is the one a person sees on the report.

    • What should I fix first on example.com?mttr_brief({ site: "example.com" })
    • Fix the top issue, then have mttr read the site again.mttr_rescan({ site: "example.com" })
    • Who am I up against, and what do they cover that I don’t?mttr_competitors({ site: "example.com" })

What you ask Codex

In words. It picks mttr’s tool for it.

Fix what is worth the most on my site.
It reads the brief, works the top fix across every page it applies to, and shows you the diff.
Did my last deploy break anything?
It asks mttr what changed since the read before, and lists any rule that now fails.
Write the answer-first opening mttr wants on /pricing.
It reads what the rule asks, rewrites the opening, and has mttr check the page.
Who am I up against?
It lists the sites doing the same work nearby, and what they cover that you do not.

Using another agent?

Codex is its maker’s product. mttr is independent and not affiliated with it. A score says pages are well formed. It does not say an assistant cites the site.

See what your agent would fix first

Free, no sign-up: a list of fixes, worth the most first.

Free, no sign-upScore, place and fixesAbout a minute

Free, no sign-up. About a minute.