Burrow + Setup MCP

Connect Cursor, Claude Desktop, or any MCP client to Burrow's Setup MCP. 23 tools automate clients, integration mappings, billing sync, report schedules, and org-wide coverage audits via setup API keys.

Request early access Read the docs

[ 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. Accept GitHub repo suggestions in one 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.

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 onboarding layer—for agents.

Burrow’s Setup MCP turns organization setup into something your coding assistant can run. Instead of clicking through client creation, integration mapping, and billing sync in the dashboard, hand a setup API key to Cursor or Claude Desktop and let the agent work through the checklist.

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

How it works

Create a setup key in Settings → Developer after joining early access.
Add the MCP config to Cursor, Claude Desktop, or your MCP runner.
Run setup tasks—create clients, apply GitHub mappings, sync Harvest billing clients, schedule monthly reports.

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

What Setup MCP handles

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

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

Quick reference

See the Setup MCP docs for tool categories, key types, and a copy-paste config snippet.

What’s next: Analytics MCP

Roadmap — not available today.

Setup MCP automates onboarding. A future Analytics MCP will let external agents query channel metrics and project health directly—tools like query_channel_metrics, get_project_health, and get_client_summary.

Example scenarios:

A coding agent in Cursor asks: “What’s the deployment frequency for harbor-14/website?”
A project management agent pulls a weekly ship summary for a client standup.

Analytics querying via MCP is on the roadmap. Setup MCP is available now.

Frequently asked questions

What is Burrow Setup MCP?

Setup MCP is a JSON-RPC endpoint at POST /api/mcp that exposes 23 tools for organization setup automation. External AI agents use a setup API key to manage clients, mappings, billing sync, report schedules, and org-wide integration coverage audits—without opening the Burrow dashboard for every step.

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

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

Can Setup MCP connect OAuth integrations?

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

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?

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, and generate reports.

Your agency's work deserves to be seen.

We're onboarding agencies in small cohorts to keep the quality high. Request early access and we'll be in touch.

Request early access Read the docs

Self-funded · Independent · Built for the long term