Docs
Documentation
Start with the studio walkthrough, then go deeper into the MCP server and your assistant's setup.
Start here
MCP server
Getting started with the aeomcp MCP server
Connect to the host you were given — production and staging are separate deployments on separate domains, and this page ships inside the server image, so it…
Authentication
Three methods, one resulting identity.
Connect your assistant
The studio's post-setup screen ("Reports & workflow") offers two independent cards once your first reports start collecting: Connect your AI assistant and Get…
Tool reference
Every tool the AEOMCP MCP server exposes to an authenticated caller, with the permission tier and scope each one requires.
Reports: get_report and get_answers_report
getreport and getanswersreport are one dimensional aggregator behind two tools. getreport(kind='brands', dimensions=[]) returns exactly getoverview's rows…
Onboarding and reports: get_onboarding_status and get_client_report
Two read tools over the agency-onboarding flow: getonboardingstatus tells you how far each of a session's brand slots has gotten (collection, analysis…
Prompt templates
Seventeen read-only prompt templates. Fifteen name the tools an agent should call, in order, to produce one deliverable, and take workspace (a name or id…
Writing through MCP
Write tools ship in six families:
Trial workflows
Five workflows an agency or brand runs during a trial100v1 trial, or explores before starting one. Each has a real-trial path (your own workspace, real…
If you know Peec's MCP
Peec and aeomcp use the same columnar idea — every analytical tool returns columns, rows, rowcount and a traceid — so most of what you already know about…
Release notes: Google AI Mode relabel and the Google AI Overview channel
What changed for MCP clients when Google collection was split into two channels (2026-09). Read this if your client stores engine names, filters by…
Connect a client
Connect ChatGPT to AEOMCP
ChatGPT: paste the AEOMCP MCP URL into its connector settings and sign in — no token — then verify the setup with one prompt.
Connect Claude (claude.ai, Desktop, Cowork) to AEOMCP
Claude (claude.ai, Desktop, Cowork): paste the AEOMCP MCP URL into its connector settings and sign in — no token — then verify the setup with one prompt.
Connect Claude Code to AEOMCP
Claude Code: connect to the AEOMCP MCP server with your access token, install the agency skills, and verify the setup with one prompt.
Connect Codex to AEOMCP
Codex: connect to the AEOMCP MCP server with your access token, install the agency skills, and verify the setup with one prompt.
Connect Other MCP client to AEOMCP
Other MCP client: connect to the AEOMCP MCP server with your access token, paste the workflow prompts below, and verify the setup with one prompt.