Developer Docs Full docs coming soon

Documentation

Comprehensive documentation is on the way. In the meantime, our SDKs and plugins are open source — explore the repos below or check the product overview for the full picture.

[ Open Source ]

Burrow SDK

PHP and TypeScript SDK monorepo — transport client, event envelope builders, contract models, durable outbox primitives, and backfill processing with retries.

More SDK languages are planned as we expand platform coverage.

PHP TypeScript

WordPress Plugin

Production plugin for WordPress — WooCommerce order/item/funnel events, Gravity Forms, Fluent Forms, Ninja Forms, Contact Form 7 ingestion, system heartbeats, and durable outbox delivery.

Extensible by design: we can continue adding coverage through additional plugin and core WordPress hooks.

PHP

Craft CMS Plugin

First-class Craft CMS integration — auto-detects your stack, ingests entry and form events, captures Craft Commerce order/item/funnel events, and backfills history via the Burrow SDK.

Hook-first architecture means we can keep expanding event capture across Craft plugins and core hooks.

PHP

[ Coming Soon ]

Statamic

Coming Soon

ExpressionEngine

Coming Soon

[ Burrow MCP ]

Automate onboarding and query analytics from Cursor.

Burrow exposes a JSON-RPC MCP endpoint so external AI agents—Cursor, Claude Desktop, or custom runners—can automate organization setup (clients, projects, integration mappings, billing client sync, CMS plugin handoff) and query channel metrics, project health, and client summaries.

Setup API key

Create in Settings → Developer. Scopes all MCP tools to your organization. Read-only or read & write access, plus an optional Analytics toggle that unlocks the metrics tools.

Ingestion API key

Separate keys for live event pipelines and CMS plugins. The Burrow MCP cannot ingest events—use ingestion keys for that.

Tool categories (38 tools — 26 setup + 12 analytics)

→ Clients & projects (list, create, update)
→ Integration mappings (discover, apply)
→ Integration coverage audit (org-wide gaps)
→ Billing sync (Harvest, FreshBooks, Tillage)
→ GitHub mapping suggestions
→ CMS plugin install instructions
→ Client report schedules & generation
→ Org overview & channel metrics
→ Project health & client summaries
→ Fleet triage (stale projects, sites behind, incidents, backup failures)
→ Period-over-period comparisons

Cursor MCP config

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

[ Analytics tools ]

Available now

Query metrics and health via MCP

Enable Analytics on a setup key and external agents get 12 read-only tools—get_channel_metrics, get_project_health, get_client_summary, and more—for channel KPIs, client briefs, fleet triage, and period-over-period comparisons. Analytics tools stay hidden from the tool list unless the key has Analytics enabled.

Example: a coding agent asks deploy frequency for a repo; a PM agent pulls a weekly ship summary for a client standup.

Create a setup key in Settings → Developer after joining early access. See the Burrow MCP integration page for a full overview, or grab a tested workflow from the starter prompts library.

Browse starter prompts

[ Event API ]

Unified event ingestion.

Every event flows through a single endpoint. Plugins, SDKs, and custom integrations all use the same envelope format — scoped by organization, client, and project.

API Request Example POST /api/v1/events

$ curl -X POST app.useburrow.com/api/v1/events \
  -H "Authorization: Bearer brw_live_xxxx_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "cli_xyz",
    "projectId": "prj_123",
    "channel": "forms",
    "event": "forms.submission.received",
    "timestamp": "2026-03-17T08:30:00.000Z",
    "properties": {
      "submissionId": "sub_456",
      "formName": "Contact"
    },
    "tags": {
      "formId": "contact"
    }
  }'

Idempotent

Deterministic event keys ensure safe retries and deduplication across outbox workers.

Multi-tenant

Organization, client, and project scoping baked into every envelope.

Durable

Local outbox with enqueue-first delivery, exponential backoff, and terminal failure handling.

[ FAQ ]

Technical FAQ

How fast can I start sending events?

For plugin installs, setup is near-zero: install, paste your API key, and events begin flowing after link/sync. For custom integrations, you can post immediately to `POST /api/v1/events` with the standard Burrow envelope.

Can I send custom events to Burrow?

Yes. Burrow exposes a single event ingestion API endpoint (`POST /api/v1/events`) that accepts a standard JSON event envelope, including custom operational events.

What sources does Burrow support today?

Today, Burrow supports the SDK, the WordPress plugin, and the Craft CMS plugin, plus direct API ingestion for custom sources. Additional integrations can publish through the same event endpoint and envelope format.

How is data scoped and isolated?

Events are scoped by organization, client, and project. Ingestion keys are tied to the linked project so event routing and access boundaries stay isolated by tenant.

Is there an SLA for Burrow?

As an early access product, we do not currently offer a formal enterprise SLA, though our infrastructure is built on highly available serverless primitives.

What's the difference between setup keys and ingestion keys?

Setup keys (brw_setup_*) authenticate external AI agents through the Burrow MCP for organization setup—clients, mappings, billing sync, report schedules, and org-wide integration coverage audits—plus analytics queries when the key has Analytics enabled. Ingestion keys authenticate live event pipelines and CMS plugins. They serve different purposes and cannot be swapped.

Ready to connect your first source?

Get started with early access. We'll walk you through setup and have you ingesting events in minutes.

Request early access Read the docs

Self-funded · Independent · Built for the long term