MCP server

aeotime's MCP server lets AI assistants read your aeotime data. Ask things like:

• "Which prompts did we lose to competitors this month?"
• "What should we fix first to show up more in Perplexity?"
• "Which AI crawlers hit errors on our site last week?"

Connect

You need an API key from API & MCP in the app (see REST API).

Claude Code

claude mcp add --transport http aeotime https://api.aeotime.com/mcp \
  --header "Authorization: Bearer aeo_YOUR_KEY"

Cursor, Windsurf, VS Code and other clients (mcp.json):

{
  "mcpServers": {
    "aeotime": {
      "url": "https://api.aeotime.com/mcp",
      "headers": { "Authorization": "Bearer aeo_YOUR_KEY" }
    }
  }
}

The server uses the Streamable HTTP transport and answers each request directly (no server-initiated messages).

Tools

Tool	What it returns
list_projects	Your projects and their ids
get_visibility_overview	Headline metrics, per engine, vs previous period
get_prompt_performance	Per-prompt visibility, position and competitors
get_competitors	Share of voice by brand
get_citations	Domains engines cite
get_content_gaps	Prompts competitors win
get_action_plan	Prioritised actions, status and impact
get_markets_and_personas	Visibility by market and persona
get_crawler_activity	AI crawler visits and errors
get_answers	Latest raw answers

Most tools take project_id, and optionally days and engine. Assistants usually call list_projects first on their own.

Security

Treat the API key like a password. Keep it out of shared repositories, use one key per tool so you can revoke them separately, and revoke keys you no longer use.