What is MCP
How the Model Context Protocol lets AI agents query AdCrunch in natural language.
MCP (Model Context Protocol) is an open standard that lets AI agents — Claude Desktop, Claude Code, Cursor, ChatGPT, and others — call structured tools exposed by external servers. AdCrunch ships an MCP server that exposes your campaigns, ads, and insights as queryable tools.
In plain terms: once you wire AdCrunch’s MCP server into your AI client, you can ask it things like “what were my top three Meta campaigns by ROAS last week?” and it knows how to call the right AdCrunch tool, pass the right parameters, and explain the answer.
What you can do with it
Ask in natural language
Skip the dashboard. Ask your AI client and get the same answer.
Compose across platforms
Compare Meta and TikTok side-by-side without exporting CSVs.
Drill into one ad group
Find the underperforming creative inside a campaign.
Plug into your workflow
Use AdCrunch from wherever your AI lives — Claude, Cursor, ChatGPT.
How it works
AdCrunch hosts a remote MCP server at mcp.adcrunch.dev. You authorize your AI
client once via OAuth; from then on, the client calls AdCrunch’s tools on your
behalf, scoped to your organization.
The tools available today
list_advertisers, list_campaigns, list_ad_groups, list_ads,
query_insights. See the Tool reference for
each.
What’s next
- Set up Claude Desktop — the most common client.
- Tool reference — what every tool does, with examples.
- Recipes — prompts that work today.