Bono MCP Server

Connect AI agents to Bono over MCP

Bono runs a remote Model Context Protocol server at https://api.heybono.ai/mcp over Streamable HTTP. Authenticate with the same bono_live_ developer API key used for the REST API — no separate signup. Works with Cursor, Claude Code, Claude Desktop, and VS Code by adding the endpoint plus an Authorization: Bearer header to the client MCP config.

29 curated, scope-filtered tools

Tools cover profile, pages, and credits; brand; training (including bono_share_training_data, reviewed by the owner before it counts); posts, topics, and the calendar; text, image, snippet, carousel, and video generation; channels, publishing to LinkedIn, X, Instagram, Facebook, and Threads, scheduling, and metrics; newsletter stats, subscribers, and sends; and webhooks. Only tools the calling key is scoped for, in modules enabled for the account, are listed.

Same credits, scopes, and rate limits as REST

Each MCP tool call executes the equivalent /v1 request as the caller, so scope checks, credit charges, channel quotas, input sanitizing, and usage accounting run through identical code. Prices match the app, every result reports credits charged and remaining, and paid tools accept an idempotency key so retries are never charged twice. MCP traffic appears in usage rollups under an mcp: route prefix.