Bono MCP Server

Connect AI agents to Bono over MCP

Bono runs a remote Model Context Protocol server at https://api.bono.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.

16 curated, scope-filtered tools

Tools: bono_get_profile, bono_list_pages, bono_get_brand, bono_update_brand, bono_get_training, bono_manage_training_evidence, bono_manage_training_reference, bono_list_posts, bono_get_post, bono_create_post, bono_update_post, bono_generate_content, bono_generate_media, bono_get_job, bono_publish_post, bono_manage_webhooks. Only tools the calling key is scoped for are listed, so agents never see a capability they cannot use.

Same credits, scopes, and rate limits as REST

Each MCP tool call executes the equivalent /v1 request as the caller, so scope checks, credit burns, input sanitizing, and usage accounting run through identical code. Creating a post or generating text costs 10 credits; a carousel costs 20 and a video 50. MCP traffic appears in usage rollups under an mcp: route prefix.