Guide

Connect an agent

Three steps: create a key, point your MCP client at the server, and confirm the tools show up. You'll need a Pro plan or higher for MCP access.

1. Create an API key

Open Settings → API keys and create a new key. Copy it immediately — the full value is shown once and only a hashed form is stored. See Authentication for details on scoping and expiry.

2. Configure your MCP client

Most clients accept a JSON server block. Add AEO with your endpoint and the key you just created.

mcp client config

{
  "mcpServers": {
    "aeo": {
      "url": "https://your-host/mcp",
      "headers": { "Authorization": "Bearer aeo_xxxxxxxx" }
    }
  }
}

Using Claude Code? The CLI does it for you:

claude code

claude mcp add --transport http aeo https://your-host/mcp \
  --header "Authorization: Bearer aeo_xxxxxxxx"

Replace https://your-host/mcp with your AEO deployment URL. The transport is HTTP and stateless, so every request must carry the Authorization header.

3. Verify the connection

Ask your agent to list its tools — you should see the read-only AEO tools, or call one directly:

example prompt

Use the aeo MCP server to list my projects, then pull visibility for the last 30 days.

Troubleshooting

401 — the key is missing, expired, or invalid. Create a new one.
403 — the account isn’t on a plan that includes MCP. Upgrade to Pro or higher.
No tools listed — confirm the URL ends in /mcp and that the header is spelled Authorization.

See what each tool returns