Fix issues with an AI coding assistant

An AI coding assistant works in your site's code. Connected to SEO Uptime, it can read what we found on the live site, change the code, and ask us to check its work. It may:

• list your team's sites, and see where each one stands (list_sites, get_site_status);
• list a site's issues, most important first (list_issues);
• read one issue in full, with what we saw on real pages (get_issue);
• get what it needs to fix one: the affected pages and what must be true afterwards (get_fix_context);
• compare two crawls, to see what a deploy changed (compare_crawls);
• record its fix, with the pull request or commit (link_fix);
• ask us to check again, and read the answer (request_recheck, get_recheck_result);
• start a full crawl, only if you allow it (start_crawl).

Our findings describe the live site, so the assistant works out which file causes each one. It is told that nothing counts as fixed until our recheck says so. A fix it records shows on the issue's page like one of yours, marked as made by your AI coding assistant.

1. Click your name, then "Your account", then the "Coding agents & API keys" tab.
2. Under "Connect a coding agent", click "Claude Code".
3. Copy the two lines and run them in a terminal. They install the SEO Uptime plugin: the connection, and a skill that tells Claude how to fix what we find.
4. The first time Claude uses SEO Uptime, your browser opens to sign in.

claude plugin marketplace add codenyra/claude-plugins
claude plugin install seouptime@codenyra

On the same tab, the "Cursor" and "VS Code" buttons open the app and add SEO Uptime to it. The first time the assistant uses it, your browser opens to sign in.

"Claude Desktop" opens the app and copies our address. In Claude Desktop, open Settings, then Connectors, choose "Add custom connector", and paste it. It then works on claude.ai too.

Any app that speaks MCP, the standard way AI assistants reach other services, connects to this address:

https://seouptime.com/mcp

In the app's MCP settings it looks like this. If the app signs in when it connects, as most do, leave out the headers lines. If it asks for a key instead, make an API key (below) and put it in place of YOUR_API_KEY.

{
    "mcpServers": {
        "seouptime": {
            "type": "http",
            "url": "https://seouptime.com/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

When an app signs in, our page asks which team it works in, under "Organization". It sees that team's sites and nothing else. Then you choose what it may do:

• Read issues and crawls. Always on: an API key that can read nothing is no use.
• Record fixes and ask for rechecks. A recheck fetches a few pages, which count against the month.
• Start crawls. A full crawl can spend a lot of the month's pages.

Fixing is ticked for you, and starting crawls is not. Leave crawls off unless you want the assistant to start them. Click "Connect" to finish.

An assistant can't change settings, hide issues or invite anyone: there is no way for it to. It may start 30 crawls or rechecks an hour at most. Everything it reads from your pages is content from your site, and it is told to treat that as data, never as instructions.

For a script, or an app that asks for a key instead of signing in.

1. On the "Coding agents & API keys" tab, under "API keys", give the key a name.
2. Pick the team, if you are in more than one, and tick what it may do.
3. Click "Create API key", and copy it at once: this is the only time it is shown.

The app sends the key as a bearer token, in the Authorization header. "Settings for an app", under the new key, shows the MCP settings with the key already filled in. A key acts as you in one team, and has an end date, shown in the list.

"Connected apps and keys", on the same tab, lists every app you signed in and every key, with its team, what it may do and when it was last used. "Disconnect" or "Revoke" stops one at once. Leaving a team, or being removed from it, ends your apps' and keys' access to that team too.

On any issue's page, under "How to fix", "Copy instructions for your developer or AI assistant" copies the problem, the pages and what we saw. Paste it into a ticket, or into any AI chat working on your site's code. Once the fix is deployed, click "I've fixed this" on the issue, as Work through issues explains.