How it works
Your agent talks to https://seo.ainomiq.com/mcp with the Model Context Protocol. You sign in once with your Ainomiq SEO account: clients with a browser open our consent screen, headless clients need device-flow support or a manual callback. Follow the instructions for your client. For CI and scripts a personal API key remains available under Advanced on the AI agents page.
Once connected, every audit page in your workspace shows a ready-made prompt. Paste it into your agent: it reads the grouped actions, the affected URLs and the evidence, fixes the findings in your code or CMS, and tests published changes together inside the original audit with test_audit_changes. The agent needs separate access to your code or CMS and must publish its changes before checking a live page. Saved tests show before/after evidence without consuming a new audit credit. A trial includes one test round during its 72 hours; a paid audit includes three rounds within 30 days.
Setup per client
OAuth setup instructions and local API-key configuration are available in your workspace under AI agents. The short version:
- ChatGPT: Settings, Security and login, turn on Developer mode and reload. Then Plugins in the sidebar, the plus at the top right (or Settings, Plugins, Plugin Management): name Ainomiq SEO, the server URL, authentication OAuth, Create. In a Work chat type @ and pick Ainomiq SEO, click Connect and sign in.
- Claude (claude.ai, Desktop, Cowork): Settings, Connectors, Add custom connector with the server URL, then Connect and sign in.
- Claude Code: claude mcp add --transport http --scope user ainomiq-seo https://seo.ainomiq.com/mcp, then claude mcp login ainomiq-seo and finish the sign-in in the browser. Or paste the prompt from the AI agents page and Claude Code does it for you.
- Cursor: one-click install from the AI agents page; the first tool call opens the browser to sign in.
- Codex: codex mcp add ainomiq-seo --url https://seo.ainomiq.com/mcp, then codex mcp login ainomiq-seo.
- OpenClaw: openclaw mcp add ainomiq-seo --url https://seo.ainomiq.com/mcp --transport streamable-http --auth oauth, then openclaw mcp login ainomiq-seo: approve in the browser; for a remote callback, follow the printed --code command in the operator terminal.
- Hermes Agent: add ainomiq_seo with the url and auth: oauth under mcp_servers in ~/.hermes/config.yaml, then hermes mcp login ainomiq_seo.
- Other clients: any MCP client that supports Streamable HTTP with OAuth sign-in (discovered automatically), or a bearer header with an API key.
What the agent can do
- list_websites and add_website: your websites, within the website allowance of your plan.
- run_audit and get_audit_status: start a scan within your allowance and follow its progress. Scans run in the background.
- get_audit_report: counts, coverage, comparison with the previous scan and the grouped actions with recommendations.
- get_audit_issues and get_audit_pages: every finding with explanation, evidence and next step, and the per-page facts.
- test_audit_changes: test original pages and save the before/after result under the audit. get_audit_verification: read progress and evidence. check_page: one-page diagnostic only.
- get_rankings: tracked keywords with their latest measured positions.
Boundaries and safety
Ainomiq SEO never edits your website. The agent you connect makes changes in your own code or CMS, and you remain responsible for reviewing them. Findings labelled as guidance are review prompts, not ranking rules, and no tool can prove Google indexing or positions.
Sign-in tokens and API keys only work with the MCP server. They cannot open your workspace, change your plan or reach payment details. Clients store access tokens and can renew them automatically. Disconnect a client or revoke a key on the AI agents page at any time. A last-activity timestamp records a previous request, not a live connection. Requests are rate limited and scans count against the same allowance as scans started in the workspace.
Troubleshooting
- The client cannot connect: check that the URL is exactly https://seo.ainomiq.com/mcp and that the Authorization header starts with Bearer aseo_.
- Sign-in loops or fails: remove the connector in your client and add it again, then disconnect the old entry under Connected clients on the AI agents page.
- The agent cannot find a website: ask it to call list_websites first and use the returned id.
- A scan does not start: your allowance for this month may be used. Plans and one-time audits are under Plan & billing in your workspace.
