connect // mcp server
Use dotmap from your AI assistant
dotmap has an MCP server, so an AI assistant can run SEO and AEO audits for you. Connect Claude, Cursor or VS Code once, sign in with Google, and then ask in plain language: audit a site, list your saved sites, see what changed since the last run, or find the weakest pages.
Server URL
https://dotmap.ai/mcpRun this in your terminal, then type /mcp in Claude Code, pick dotmap and choose Authenticate.
claude mcp add --transport http dotmap https://dotmap.ai/mcpThe first time, your app opens a browser so you can sign in to dotmap with Google and approve access.
tools // 10 total
What your assistant can do
The server exposes ten tools. You never call them by name; the assistant picks the right one from what you ask.
- audit_site
- Audits up to 25 pages of a public site and returns the score, top issues, weakest pages and a report link.
- start_audit
- Queues a larger background audit, sitemap first, of up to 5,000 pages and returns a job id straight away.
- get_audit_status
- Shows progress for a running audit, then the report summary and links once it finishes.
- list_sites
- Lists your saved sites with their latest score and last audit time.
- get_site
- Returns up to 20 recent audits for one site, with scores and report links.
- get_pages
- Lists pages from an audit with score, grade, citability and issues, filtered and sorted as you ask.
- get_changes
- Compares the last two audits: pages that regressed or improved, broke or were fixed, and issues that are new or resolved.
- get_report
- Reads the public view of a shared report from its link.
- get_monitor
- Shows a site's monitoring settings, last and next run, and recent regression alerts.
- set_monitor
- Turns continuous re-auditing on or off and sets its frequency, size and alert threshold.
access // oauth
You approve access once
The first request from your assistant opens a browser window. You sign in with Google, see which app is asking and what it wants to do, and choose Allow. dotmap uses the standard OAuth flow for MCP, so there is no API key to copy or store.
Access is split in two: reading your sites and reports, and starting audits or changing monitoring. An app that only asked to read cannot start a crawl.
scope // your account only
Your data stays yours
Every tool runs as the signed-in user and only returns that account's sites, audits and monitors. Asking for another account's site returns nothing.
Only public websites can be audited. The crawler refuses private and internal addresses, and audits count against the same hourly and daily limits as the website.
faq
Questions about connecting
- What is the dotmap MCP server?
- It is a Model Context Protocol endpoint that lets an AI assistant use dotmap directly. Once connected, the assistant can audit a site, list your saved sites, compare two runs, find weak pages and read reports, without you opening the dotmap website.
- Which AI assistants can connect to dotmap?
- Any client that supports remote MCP servers over HTTP with OAuth sign-in. Setup steps are given above for Claude Code, Claude on the web and desktop, Cursor and VS Code, plus a JSON config for other clients.
- Do I need an account?
- Yes. The first time your assistant connects, a browser window opens for you to sign in with Google and approve what the assistant may do. Audits it runs are saved to your account.
- What can a connected assistant see?
- Only your own account: your saved sites, audits, pages and monitors. It cannot read another user's data. If you grant read-only access, the assistant can read results but cannot start audits or change monitoring.
- What are the limits?
- A quick audit covers up to 25 pages and returns in under a minute. Background audits cover up to 5,000 pages. Each account can run 10 audits an hour and 40 a day, and save 10 sites on the free plan.