Kampalo MCP server

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.

This plugin does not add product APIs. It wires Grok to python manage.py runmcpserver:

• Read tools from marketing/agents/suites.py (synced Postgres)
• automate tools from marketing/agents/automationbackend.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_*.

Installation

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 KAMPALOMCPAPIKEY 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 userid or useremail. Ask the user if neither is known. A personal key already binds your user, so you can omit both.

Cursor

The same repo ships Cursor packaging next to the Grok files. Both use the same skills/ and the same MCP server.

1. Generate a key in Kampalo Settings → API Keys.
2. 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

1. 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.

Claude (claude.ai, Cowork, Claude Code)

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 KAMPALOMCPAPIKEY to set. Its skills are a copy of skills/ without the userid / 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.

Network and credentials

The plugin talks only to that MCP host. It does not read local .env / SSH keys or send telemetry elsewhere.

What Grok can do

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.

Shortened. The full README is on GitHub.