Run Burrow from your agent.

Connect Cursor, Claude Desktop, or any MCP client to the Burrow MCP — 38 tools that automate client onboarding, billing sync, reports, and health queries.

Request early access Browse starter prompts

Works with Cursor & Claude Desktop
Org-scoped setup keys
Read-only keys available
Revoke anytime

Works with your favorite AI tools

Claude
Cursor
OpenAI
Gemini
Windsurf
Copilot

[ Connect in two minutes ]

How to connect Burrow MCP

1

Create a setup key

In Settings → Developer, create a setup API key. Choose read-only or read & write access, and toggle Analytics on if your agent should query metrics and client health.
2

Add the MCP config

Paste the generated config into Cursor, Claude Desktop, or your MCP runner. One URL, one Bearer token — no OAuth dance, no local server to run.
3

Put your agent to work

Create clients, apply GitHub mappings, sync Harvest billing, schedule monthly reports — then ask how Client X is doing and get a cross-channel answer.

[ Prompt your agent ]

Say it like you'd say it to a teammate

New chat — Burrow MCP connected

mcp

Use Burrow to set up a monthly report for Client X — schedule it to go out on the first of the month, and generate a draft now so I can review it first.

What happens One prompt. Your agent creates the report schedule, sets the recipients and send date, and emails you a draft — you never open the dashboard.

[ Capabilities ]

Clients & projects

List, create, and update Burrow clients and projects from your agent. Bulk-create clients from unmapped billing sources. Read onboarding checklist progress to see what's left.

Integration mappings

Discover unmapped provider sources and apply mappings to projects. Audit integration coverage org-wide—find connected-but-unmapped GitHub, analytics, and monitoring sources across all clients in one agent call.

Billing sync

List, sync, and map billing clients from Harvest, FreshBooks, and Tillage. Bulk-create Burrow clients from unmapped billing records and accept suggested mappings.

Report schedules

List, create, and update client report schedules. Generate reports and email recipients—all from an external agent with a read & write setup key.

Analytics & client health

Query channel KPIs, per-project drill-downs, and period-over-period deltas. Ask for a one-call client brief—'how is Client X doing?'—and get metrics across every connected channel.

Fleet triage

Surface stale projects, CMS sites behind on updates, open monitoring incidents, and backup failures across the whole org. Your agent finds the fires before the client does.

Example

Add to your Cursor or Claude Desktop MCP settings

{
  "mcpServers": {
    "burrow": {
      "url": "https://app.useburrow.com/api/mcp",
      "headers": {
        "Authorization": "Bearer brw_setup_YOUR_KEY_HERE"
      }
    }
  }
}

Your agency’s operations layer—for agents.

Burrow’s MCP server puts organization setup and agency analytics in reach of your coding assistant. Hand a setup API key to Cursor or Claude Desktop and the agent can work through the onboarding checklist—create clients, map integrations, sync billing—then turn around and answer “which clients are behind on updates and haven’t shipped anything this month?”

This is the developer path into Burrow—complementing CMS plugins (for event ingestion) and Scout (Burrow’s in-app agent). The MCP endpoint is for external agents that already live in your editor or terminal.

Every tool runs in the organization bound to your setup key, and list and discover responses include organizationId so agents can verify they are operating in the correct org.

What the MCP handles

38 tools — 26 for setup, 12 for analytics. Setup tools automate onboarding and configuration; analytics tools answer questions about the org your setup work built.

Area	Capability
Clients & projects	List, create, update
Setup progress	Read onboarding checklist state
Integrations	Discover and map external sources to projects
Coverage audit	Org-wide gap matrix—connected-but-unmapped providers across all projects
Billing	List, sync, and map Harvest, FreshBooks, Tillage clients
CMS plugins	Fetch install instructions per project
GitHub	Accept suggested repo → project mappings
Reports	List, create, update schedules; generate and email
Org overview	Cross-channel dashboard pulse: incidents, updates, KPI summaries
Channel metrics	Per-channel KPIs and per-project drill-downs, with date ranges
Project & client health	Health rollups, client briefs, recent activity streams
Fleet triage	Stale projects, sites behind on updates, open incidents, backup failures
Comparisons	Period-over-period deltas for any channel

OAuth connects, live event ingestion, team admin, and org-level report templates stay in the dashboard.

Analytics tools: ask how your clients are doing

Enable Analytics on a setup key and your agent gets 12 read-only tools that mirror the Burrow dashboards:

Tool	What it does
`list_channels`	List the channel keys (core + custom) available for metrics queries
`get_org_overview`	Org-wide pulse: open incidents, pending updates, per-channel KPI summaries
`get_channel_metrics`	Channel KPIs matching the Burrow dashboards—analytics, monitoring, code, forms, ecommerce, backups, invoicing, and more
`get_project_channel_detail`	Per-project drill-down for one channel—KPIs, health, per-form/workflow/repo detail
`get_client_summary`	One-call multi-channel brief for a client—“how is Client X doing?”
`get_recent_activity`	Recent event stream across channels, filterable by client, project, or channel
`get_project_health`	Cross-channel health for one project: CMS updates, incidents, backup failures, stale repos, cert expiry
`list_stale_projects`	Projects with no or old activity
`list_sites_behind`	CMS sites needing updates—Craft, WordPress, Statamic
`list_open_incidents`	Currently open monitoring incidents
`list_backup_failures`	Backup jobs with failures plus upcoming expirations
`compare_periods`	Period-over-period deltas for a channel

Things agents can do today:

A coding agent in Cursor asks “What’s the deployment frequency for harbor-14/website?”—get_project_channel_detail on the code channel answers it.
A project management agent pulls a weekly ship summary for a client standup—get_client_summary plus get_recent_activity, one prompt.
A morning triage run: stale projects, sites behind on updates, open incidents, and backup failures across every client, before you’ve opened a dashboard.

Analytics tools require a key with Analytics enabled—they stay hidden from the tool list otherwise. Since they’re read-only by nature, a read-only key with Analytics on is a zero-write-risk way to give a reporting agent full metrics access.

Starter prompts

Not sure what to run first? The starter prompts library has tested, copy-paste workflows for the most common agency tasks — morning fleet triage, client health briefs, integration coverage audits, new-client onboarding, billing sync, and monthly report setup. Each one tells you which key type it needs and opens with the full prompt ready to paste into Cursor or Claude Desktop.

Quick reference

See the Burrow MCP docs for tool categories, key types, and a copy-paste config snippet, or grab a starter prompt and run it.

Frequently asked questions

What is the Burrow MCP?

The Burrow MCP is a JSON-RPC endpoint at POST /api/mcp that exposes 38 tools — 26 for organization setup and 12 for analytics. External AI agents use a setup API key to manage clients, mappings, billing sync, and report schedules, and to query channel metrics, project health, and client summaries — without opening the Burrow dashboard for every step.

Can external agents query analytics through MCP?

Yes. Create a setup key with Analytics enabled in Settings → Developer and your agent gets 12 analytics tools: org overview, channel metrics, per-project drill-downs, client summaries, recent activity, project health, stale-project and sites-behind lists, open incidents, backup failures, and period-over-period comparisons.

What's the difference between a setup key and an ingestion key?

Setup keys (brw_setup_*) authenticate MCP tools for onboarding, configuration, and analytics queries. Ingestion keys authenticate live event pipelines and CMS plugins. They are separate on purpose—the Burrow MCP cannot ingest events.

Can the Burrow MCP connect OAuth integrations?

No. OAuth and API-key connections require the Burrow Settings UI. Once an integration is connected, the Burrow MCP can discover sources, apply mappings, sync billing clients, and query the metrics those integrations produce.

Which MCP clients work with Burrow?

Any MCP-compatible client—Cursor, Claude Desktop, or custom runners. Create a setup key in Settings → Developer, copy the generated config snippet, and point your agent at the /api/mcp endpoint.

What are read-only vs read & write setup keys?

Keys have two dimensions. Access: read-only keys can list clients, check setup progress, discover sources, and read report configs; read & write keys add create/update operations—apply mappings, sync billing, upsert report schedules, generate reports. Analytics: an optional toggle that adds metrics access. Analytics tools stay hidden from the tool list and are rejected on call unless the key has Analytics enabled.

Is there a safe way to give a reporting agent metrics access?

Yes—create a read-only key with Analytics enabled. Analytics tools are read-only by nature, so a reporting or PM agent can pull channel metrics, client summaries, and health rollups with zero write risk. If it's ever misused, revoke the key in Settings → Developer.

[ Related ]

Use case

Unified agency operations dashboard for every client signal

Stop switching between WordPress admin, GitHub, and Stripe for each client. Burrow unifies deploys, forms, orders, payments, and uptime in one timeline.

Channel

No channel for it? Build your own.

Name your own events, pull any HTTP feed with a no-code connector, and build KPIs and breakdowns with the widget builder — a reporting channel for anything.