Kampalo plugin for Grok Build
Grok Build plugin that connects to Kampalo’s hosted FastMCP server. Grok can read synced ads/SEO/GA4 data and run the automations Kampalo already has: pause proposals, ads/SEO alerts, ROAS pause rules, and report JSON.
Potencialize seu agente
A URL do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
https://be.kampalo.com/mcpO botão do Claude acima abre o Claude com o nome e a URL preenchidos. Você ainda precisa confirmar lá.
claude mcp add --transport http com.kampalo-kampalo https://be.kampalo.com/mcpRun in a terminal.
{ "mcpServers": { "com.kampalo-kampalo": { "command": "npx", "args": [ "-y", "mcp-remote", "https://be.kampalo.com/mcp" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Grok Build plugin that connects to Kampalo’s hosted FastMCP server. Grok can read synced ads/SEO/GA4 data and run the automations Kampalo already has: pause proposals, ads/SEO alerts, ROAS pause rules, and report JSON.
Google Ads, Meta Ads, GA4, Search Console and Shopify insights, alerts, ROAS rules and ad actions.
This plugin does not add product APIs. It wires Grok to python manage.py run_mcp_server:
marketing/agents/suites.py (synced Postgres)automate_* tools from marketing/agents/automation_backend.py (same services as /api/marketing/actions/, alert rules, automation rules, reports)In-app Kai (LangGraph) stays read-only. Only this MCP catalog has automate_*.
After the plugin is listed in the xAI marketplace, in Grok Build run /plugin, search Kampalo, and install.
Until then, install from the plugin repo:
grok plugin install Tekreign/kampalo-cursor-plugin
Set KAMPALO_MCP_API_KEY to your personal kmp_… key from Kampalo Settings → API Keys (Starter and Enterprise). On first tool use Grok calls https://be.kampalo.com/mcp with Authorization: Bearer ….
Every tool also needs a Kampalo user_id or user_email. Ask the user if neither is known. A personal key already binds your user, so you can omit both.
The same repo ships Cursor packaging next to the Grok files. Both use the same skills/ and the same MCP server.
Generate a key in Kampalo Settings → API Keys.
Set it in the environment Cursor starts from, then restart Cursor:
setx KAMPALO_MCP_API_KEY "kmp_..."
export KAMPALO_MCP_API_KEY="kmp_..." # in ~/.zshrc or ~/.bashrc
Install the plugin from this repo in Cursor. Check Settings → MCP shows kampalo connected, then ask: Brief Google vs Meta in Kampalo.
Without the plugin, the same server works from a project or user ~/.cursor/mcp.json by copying the kampalo entry from mcp.json.
The Claude plugin lives in claude/ and is what the Claude directory lists. It uses OAuth: Claude asks you to sign in to Kampalo the first time, so there is no KAMPALO_MCP_API_KEY to set. Its skills are a copy of skills/ without the user_id / user_email step, because the signed-in account is applied automatically. Keep both copies in sync when you edit a skill.
Install in Claude Code from this repo's marketplace (.claude-plugin/marketplace.json points at ./claude):
/plugin marketplace add Tekreign/kampalo-cursor-plugin
/plugin install kampalo@kampalo
Run /mcp, choose kampalo, and sign in to Kampalo when prompted.
The plugin talks only to that MCP host. It does not read local .env / SSH keys or send telemetry elsewhere.
With MCP up and a Kampalo user who can mutate data (admin, or enterprise manager/marketer) for confirms. Alert/automation rule writes are admin only.
confirm=true) — writes PAUSED to Google or Metaconfirm_live=truekampalo-cursor-plugin/
├── .grok-plugin/plugin.json
├── .mcp.json
├── .cursor-plugin/plugin.json
├── mcp.json
├── .claude-plugin/plugin.json
├── .claude-plugin/marketplace.json
├── skills/campaign-performance-brief/
├── skills/automate-kampalo-work/
├── assets/logo.svg
├── LICENSE
└── README.md
Read
Use my Kampalo email
[email protected]. Brief Google vs Meta. Which campaigns have the worst ROAS?
Propose (no live pause)
Propose pausing the worst ROAS Google campaign. Do not confirm yet.
Expect automate_propose_pause and a pending action_id. The live campaign status must stay ENABLED.
Confirm (live pause)
Confirm pause for action
<id>.
Expect automate_confirm_action with confirm=true. Campaign becomes PAUSED (needs valid Google/Meta tokens).
Watchdog
Create a dry-run rule: pause Google campaigns if ROAS stays below 1 for 3 days with at least $10 spend. Do not enable live.
Expect automate_upsert_automation_rule with dry_run=true, is_active=false.
Failure
Stop MCP and ask again. The bot must not claim a pause or a saved rule.
MIT
Google Ads, Meta Ads, GA4, Search Console and Shopify insights, alerts, ROAS rules and ad actions.
{ "mcpServers": { "com.kampalo-kampalo": { "url": "https://be.kampalo.com/mcp", "headers": {} } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração http para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Kampalo é acessado por HTTP.
Última verificação: 2026-11-08. Google Ads, Meta Ads, GA4, Search Console and Shopify insights, alerts, ROAS rules and ad actions.