Developer integrations
Ask Claude about your ads—on Kampalo’s snapshot
MCP (Model Context Protocol) exposes the same marketing tools Kai uses inside Kampalo. Your agent asks about Google Ads and Meta; answers come from workspace data you already synced, with the same ROAS, CTR, and CPC ranking rules.
Why not a raw Google Ads MCP?
A per-platform MCP hands the model raw rows and leaves metric definitions to the prompt. Kampalo MCP sits on the governed snapshot: Google and Meta already aligned, currencies labelled, organic kept off paid ROAS. The model asks for a ranking; it does not reinvent CPA.
Who should use it
- Teams that already work in Claude, Cursor, or another MCP client
- Custom workflows that need Kai-style answers outside the Kampalo chat screen
- Not required for marketers who only use Kai in the app
What it will not do
MCP does not open a live Google or Meta session while you type. It does not pause campaigns from chat. Refresh connections in Kampalo when you need a newer extract. Setup details live in documentation.
FAQ
What is Kampalo MCP?
MCP (Model Context Protocol) lets developer tools such as Claude or Cursor call the same marketing tools Kai uses inside Kampalo, against your already-synced workspace data.
Does MCP query Google Ads live?
No. Like Kai chat, MCP tools read stats already synced into Kampalo. Refresh integrations in the app when you need a newer snapshot.
Who is MCP for?
Teams that want Kai-style answers inside their own agent workflow. Marketers who only need chat should use Kai in the Kampalo app—no MCP setup required.