MCP server

Let AI agents run review-request campaigns through the Model Context Protocol, with the same auth and plan limits as the REST API.

Connecting

The server speaks MCP over streamable HTTP and is authenticated with your API key as a bearer token. Point any MCP client at the endpoint:

{
  "mcpServers": {
    "reviewbump": {
      "type": "http",
      "url": "https://api.reviewbump.co/mcp",
      "headers": { "Authorization": "Bearer rb_live_your_key" }
    }
  }
}

In clients that support remote MCP connectors (e.g. Claude), add the URL above and supply the same Authorization header.

Tools

• list_organizations — your organizations and review links.
• get_usage — plan and remaining monthly text quota.
• preview_campaign — dry run: how many numbers are valid, the exact message, and whether it fits your quota — without sending or spending anything. Args: organizationId, recipients.
• create_campaign — send the preset review-request SMS to a list of numbers for an organization. Args: organizationId, recipients, optional name, optional idempotencyKey (reuse it to make a retry safe).
• list_campaigns — recent campaigns with status and counts.
• get_campaign— a single campaign's status and counts.
• get_campaign_recipients — per-number delivery status.
• cancel_campaign — stop a still-sending campaign; unsent numbers are skipped and refunded.

A good agent flow: list_organizations → preview_campaign to confirm the list and quota → create_campaign with an idempotencyKey → get_campaign to watch it finish.

Tools return JSON. Business-rule problems (no active plan, over quota, unknown organization) come back as tool errors with a clear message, so an agent can react and retry sensibly.

Quick test

You can exercise the endpoint directly with curl:

curl -X POST https://api.reviewbump.co/mcp \
  -H "Authorization: Bearer rb_live_your_key" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'