Kampalo MCP server

One MCP server for Google Ads, Meta Ads, GA4 and Shopify

MCP (Model Context Protocol) is how AI assistants reach your Kampalo workspace. The Kampalo server is hosted, verified in the official MCP Registry, and ships as a plugin in Claude, ChatGPT, Gemini, Grok and Glama. Answers come from data you already synced. Pauses and budget changes wait for your confirm.

com.kampalo/kampalo

v0.3.0

Google Ads, Meta Ads, GA4, Search Console and Shopify insights, alerts, ROAS rules and ad actions.

Activebe.kampalo.com/mcpStreamable HTTP

Auto-listed

MCP clients and directories that read the registry find Kampalo without a manual entry.

Authentic

Only kampalo.com can publish under the com.kampalo namespace.

Always current

One registry entry. Every client that reads it gets the same endpoint and version.

Trusted

A verified listing procurement and security teams can check themselves.

Install it in your AI assistant

Pick your assistant for step-by-step setup. Every plugin connects to the same server and the same tools.

Cursor

Install the plugin from the Kampalo repo (Cursor 3.13+), or copy the kampalo entry into ~/.cursor/mcp.json.

VS Code and GitHub Copilot

Find com.kampalo/kampalo through the MCP Registry, or add the endpoint as an HTTP server.

Any MCP client

Point it at https://be.kampalo.com/mcp (streamable HTTP) with a personal kmp_ key as the Bearer token.

Endpoint and authentication

Endpoint
https://be.kampalo.com/mcp — not /api, which is the REST API
Transport
Streamable HTTP
OAuth 2.1
Claude, ChatGPT and Gemini. You sign in to Kampalo once and choose Allow. No key to copy.
Personal API key
Grok, Cursor and other clients. Generate a kmp_ key in Settings → API Keys and send it as Authorization: Bearer.
Plans
Starter and Enterprise. Free cannot connect.
Registry name
com.kampalo/kampalo v0.3.0
Generic MCP client config
{
  "mcpServers": {
    "kampalo": {
      "type": "http",
      "url": "https://be.kampalo.com/mcp",
      "headers": { "Authorization": "Bearer kmp_..." }
    }
  }
}

Read tools (25)

Every read comes from the synced Kampalo snapshot, limited to the accounts and clients your role can see.

Google Ads

Campaigns, account summary, daily trends and creative fatigue.

  • google_ads_get_campaigns
  • google_ads_get_summary
  • google_ads_get_trends
  • google_ads_get_fatigue

Meta Ads

Facebook and Instagram ad campaigns, summary and fatigue.

  • meta_ads_get_campaigns
  • meta_ads_get_summary
  • meta_ads_get_fatigue

Cross-platform

Google vs Meta side by side, with currencies labelled.

  • meta_insights_get_overview
  • meta_insights_compare_platforms
  • meta_insights_get_fatigue

GA4

Traffic, AI referrals (ChatGPT, Perplexity, Gemini), organic ROI and checkout funnel.

  • analytics_get_ga4_metrics
  • analytics_get_ai_referrals
  • analytics_get_organic_roi
  • analytics_get_checkout_funnel

Search Console / SEO

Queries, pages, Lighthouse audits, metadata and paid vs organic overlap.

  • search_get_metrics
  • search_get_top_queries
  • search_get_lighthouse
  • search_get_page_metadata
  • search_get_paid_organic

Facebook Page / Instagram

Organic reach, engagement, followers and top posts. Kept off paid ROAS.

  • meta_organic_get_overview
  • meta_organic_get_page_insights
  • meta_organic_get_page_posts
  • meta_organic_get_ig_insights
  • meta_organic_get_ig_media

Shopify

Store overview: revenue, orders and products beside your ads.

  • shopify_get_overview

Automation tools (15)

These change Kampalo records. Only a confirmed pause or budget change is sent on to Google Ads or Meta.

Campaign actions

Propose a pause or a daily-budget change, then confirm or dismiss it. Nothing reaches Google or Meta until you confirm.

  • automate_propose_pause
  • automate_propose_budget
  • automate_confirm_action
  • automate_dismiss_action
  • automate_list_actions

Ads alerts

ROAS, CPA and spend-pace alerts after each hourly sync. Alerts notify; they never pause.

  • automate_list_alert_rules
  • automate_upsert_alert_rule
  • automate_delete_alert_rule

SEO / AEO alerts

Search Console and AI-referral alerts. Notify only.

  • automate_list_seo_alert_rules
  • automate_upsert_seo_alert_rule
  • automate_delete_seo_alert_rule

ROAS pause rules

Pause when ROAS stays below a threshold for N days. New rules start in dry-run and inactive.

  • automate_list_automation_rules
  • automate_upsert_automation_rule
  • automate_delete_automation_rule

Reports

Performance report JSON from synced data. The PDF stays in the Kampalo app.

  • automate_generate_report

Guardrails

  • Every pause and budget change is a proposal first. The live campaign is untouched until you say confirm.
  • Budget changes are capped at ±20% of the current daily budget, with a 24-hour cooldown per campaign.
  • Shared Google budgets, campaigns without a daily budget, and campaigns outside your selected catalog are refused.
  • ROAS pause rules start in dry-run. Going live needs an explicit confirm_live.
  • Confirms need a role that can change data. Alert and rule changes are admin only.
  • Access is limited to your Kampalo account, plan and role. Free cannot connect.

What it will not do

  • Connect new Google, Meta or Shopify accounts (do that in the Kampalo app)
  • Create campaigns, ads or audiences
  • Change budgets by more than 20% in one step
  • Write to Shopify or TikTok
  • Call the Google or Meta API live while you chat. Reads come from the synced snapshot

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. Actions go through the same proposal and confirm flow as the Kampalo app.

FAQ

What is the Kampalo MCP server?

A hosted MCP (Model Context Protocol) server at be.kampalo.com/mcp. It is how Claude, ChatGPT, Gemini, Grok, Glama, Cursor and other MCP clients reach your Kampalo workspace. Read tools cover Google Ads, Meta Ads, GA4, Search Console, Facebook Page / Instagram and Shopify. Write tools propose and confirm pauses and budget changes, manage alert and ROAS rules, and generate report JSON.

Is Kampalo in the official MCP Registry?

Yes. It is published and verified as com.kampalo/kampalo in the official MCP Registry (registry.modelcontextprotocol.io). Only kampalo.com can publish under that namespace.

Is there a Google Ads MCP server that also covers Meta Ads?

Kampalo is one MCP server for Google Ads, Meta Ads, GA4, Search Console and Shopify. Google and Meta are already aligned, currencies are labelled, and organic is kept off paid ROAS, so the model does not have to reconcile two raw APIs.

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. Confirmed pauses and budget changes still go through Kampalo to Google or Meta after you approve.

How do I authenticate?

Claude, ChatGPT and Gemini sign in with OAuth: you log in to Kampalo once and choose Allow. Grok, Cursor and other clients use a personal kmp_ key from Settings → API Keys as an Authorization: Bearer header. Both are scoped to your account, plan and role.

Who is MCP for?

Teams that already work in an AI assistant and want briefs plus confirmed automations without opening the Kampalo app. Marketers who only need answers can use Kai in the app, which stays read-only.