Developers

MCP server

Connect an assistant to RevBuddy using Streamable HTTP and the same workspace API key, scopes and Cluster eligibility as REST. Every tool calls the same operation as the API.

Connection settings

Set the server URL and an Authorization: Bearer header, or xi-api-key. There is no OAuth sign-in or separate MCP account. The placeholder below represents a key supplied through your client's secret settings; use its supported environment-variable syntax.

{
  "mcpServers": {
    "rev-buddy": {
      "type": "http",
      "url": "https://revbuddy.radioworkflow.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_REVBUDDY_API_KEY"
      }
    }
  }
}

For a command-line client with the key already in an environment variable:

claude mcp add --transport http rev-buddy https://revbuddy.radioworkflow.com/api/mcp \
  --header "Authorization: Bearer $REVBUDDY_API_KEY"

Permissions and behavior

The Bash example follows the Claude Code HTTP setup. Other clients may use a different configuration format.

• tools/list returns only the tools allowed by this key's scopes. Each call rechecks the key, plan and workspace ownership. Revoked keys stop working.
• Writes and spending happen when called. Destructive annotations help the client explain consequences; they do not create an approval step. Review publishing, generation and deletion requests before authorizing them.
• Spending operations require the idempotencyKey argument, with 8 to 128 letters, digits, dots, colons, underscores or hyphens. Reuse it for retries of the same request so a timeout does not create another charge.
• POST is the only transport method. The server issues no session ID and offers no standalone SSE stream. Send one JSON-RPC message per request.
• Requests are bounded at 256 KiB and tool results at 192 KiB. Use smaller result pages or REST for larger responses.
• A tool call uses two authorization checks against the shared limits of 60 per key and 300 per workspace each minute. This allows up to 30 tool calls per key before discovery, resource requests or other traffic. Respect Retry-After on HTTP refusals or retryAfterSeconds in a tool error when a limit is reached.
• Audio download links require the same key in an HTTP header. Audio is not returned as base64 in tool results. The server never fetches an arbitrary URL supplied by a client.

resources/list also exposes the API reference and OpenAPI document. These resources contain contract metadata, not customer records. Customer and advertiser text in operation results is data, not instructions to follow.

REST-only operations

• audio_preview_download: Binary download; use audio metadata/tool resource link and fetch with same API key
• audio_finished_download: Binary download; use audio metadata/tool resource link and fetch with same API key