Developer Platform

Build with Bupple

Bupple has no public REST API; it connects to your software through MCP in both directions, signed webhooks for every event in a workspace, Canva, and your own AI provider keys on Enterprise.

Set up webhooks MCP access

MCP and personal tokens

Bupple is an MCP server. A personal token lets Claude Desktop, Cursor or your own agent use your workspace, with only the permissions you gave it.

How MCP access works

Webhooks

Get a signed POST at your URL when something happens — a post goes out, a file lands, an automation run finishes, a campaign reaches its goal.

View Webhooks

Integrations

Seven social networks, Canva, remote MCP servers in your agents, and your own AI provider keys on Enterprise.

Browse Integrations

Quick Start

Connect your AI tool in one config entry

Point your MCP client at Bupple and send a personal token as a bearer header. What the token may do is what you ticked when you made it. MCP is on the SMB, Agency and Enterprise plans. The screen for making tokens is switched off in the app for now, so talk to us if you need MCP today.

MCP and personal tokens Webhooks Integrations Plans and pricing

.cursor/mcp.json

// .cursor/mcp.json — the token starts with bmcp_
{
  "mcpServers": {
    "bupple": {
      "url": "https://api.bupple.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer bmcp_your-token"
      }
    }
  }
}

MCP

Both ways: your tools in, your agents out

Signed

Every webhook delivery, HMAC-SHA256

Tries per webhook delivery, over about 8.6 hours

Ready to build with Bupple?

Add a webhook in Settings › Webhooks, or talk to us about MCP access.

Add a webhook Contact us

No credit card required · Cancel anytime