Connect your AI assistant

What your assistant can read

Everything BetterEO knows about your site

Crawler and AI bot analytics: who visits, which pages and which format they got.
AI interactions: pages assistants fetched to answer a prompt and visits from AI answers.
SEO and AEO scores and findings for each page, without and with BetterEO.
Security scan results, with what BetterEO fixes and what needs a change on your site.
The prerendered pages BetterEO serves crawlers.

Available tools

Every tool is read-only and only sees the project the token belongs to.

list_domains: Lists the project’s domains and their status, including whether rendering is paused.
get_analytics: Crawler and AI bot visits over a period (daily volume, top bots, top pages, countries, cache performance and what was served to each bot) and AI interactions: pages AI assistants fetched to answer prompts, visits from AI assistants, and AI search and training crawls.
list_seo_aeo_analyses: The SEO and AEO score of every analysed URL, with and without BetterEO, plus the domain averages.
get_url_analysis: The full latest analysis of a URL: findings, evidence and improvement suggestions.
get_security_scan: The latest security scan results, with and without BetterEO, and their findings.
get_cached_page: The prerendered page BetterEO serves to crawlers for a URL.

Set up in a minute

Create a token, then add the server

Create a token in the console under Project settings → AI assistants (MCP), and add the server to your assistant. The server address is https://mcp.bettereo.com/mcp, and every request sends your token in the Authorization header. Replace <token> below with your token.

Open Settings in your project and select AI assistants (MCP).
Select Create token and give it a name, for example the assistant and the computer it runs on.
Copy the token or one of the ready-made snippets right away: the token isn’t shown again.

Claude Code

Run this command in your terminal.

claude mcp add --transport http bettereo https://mcp.bettereo.com/mcp --header "Authorization: Bearer <token>"

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in your project.

{
  "mcpServers": {
    "bettereo": {
      "url": "https://mcp.bettereo.com/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

VS Code

For GitHub Copilot agent mode, add this to .vscode/mcp.json in your project.

{
  "servers": {
    "bettereo": {
      "type": "http",
      "url": "https://mcp.bettereo.com/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Other clients: any client that supports remote MCP servers over Streamable HTTP with a custom Authorization header can connect with the same address and header. Support for custom headers varies, so check your client’s documentation.

What you can ask

Ask it to find what to fix

Your assistant reads your project’s data and suggests fixes, and the code changes happen in your own codebase.

“Find the pages with the lowest AEO score on my site and suggest fixes.”
“Which AI crawlers visited last week, and which pages did they read?”
“Fix the security findings that need a change on my site.”

Security and access

Read-only and per project

Each token reads one project and can’t change anything. It is shown once, stored only as a hash, and you can revoke it at any time.

Read-only: assistants can read your data but can’t change anything in BetterEO.
Scoped: a token only gives access to the project it was created in.
Revocable: revoke a token at any time in Settings → AI assistants (MCP); access stops immediately.
Secret: the token is shown once. Treat it like a password, keep it out of repositories and create a new one if it leaks.

Keep exploring