Maak mijn eerste campagne
Menu van de documentatie
API

MCP server

Connect Claude, Cursor or ChatGPT to BannerMotion: 10 tools to generate, correct, view and export banners.

BannerMotion is also a remote MCP (Model Context Protocol) server: an AI assistant can generate, correct, view, adapt and export banners on your behalf, with the same permissions and credits you have in the app. The transport is Streamable HTTP and the address is:

https://app.bannermotion.com/mcp
Opmerking. This is the address our documentation declares for the server. [PLACEHOLDER: confirm the final domain; it will also be available at mcp.bannermotion.com later]

Connect a client

  • Claude.ai (web and desktop): in "Settings → Connectors → Add custom connector" paste the address and click Connect. BannerMotion opens so you can choose the workspace. On team plans, an administrator adds the connector for the organization.
  • Claude Code: claude mcp add --transport http bannermotion https://app.bannermotion.com/mcp and, inside Claude Code, /mcp → bannermotion → Authenticate.
  • Cursor: copy the JSON on the right into ~/.cursor/mcp.json (or the project's .cursor/mcp.json) and connect from "Settings → MCP".
  • ChatGPT: "Settings → Apps & Connectors → Advanced → Developer mode → Create", with the address and OAuth authentication.

Authentication

  • OAuth 2.1 (recommended): the client registers itself, opens the "Connect an application" screen, you choose the workspace and approve. It uses PKCE. Access lasts 1 hour and renews itself (the refresh token lasts 30 days). The connection appears in your account as an "MCP · client" session and ends when you sign it out. If the workspace requires two-step verification, turn it on before connecting.
  • API key bm_live_… in Authorization: Bearer …. Its permissions limit the tools. bm_test_… keys do not work with MCP.
Claude Code with an API key
claude mcp add --transport http bannermotion https://app.bannermotion.com/mcp \
  --header "Authorization: Bearer $BM_API_KEY"

The 10 tools

ToolWhat it doesKey permission
list_campaigns
Lists the workspace's campaigns, with sizes, locales and pieces.
read
list_banners
Lists a campaign's concepts, with their pieces and approval status.
read
generate_banner
Generates a concept from a plain-language request. Returns the job; with wait_seconds it waits for it to finish. Spends credits.
generate
get_job
Status of a job (queued, running, done or failed), with optional waiting.
read
edit_banner
Corrects a concept with an instruction, optionally only in some sizes. Spends credits.
generate
preview_banner
An image of a frame and a signed link (1 hour) to watch the whole animation.
read
add_sizes
Adapts a concept to new sizes. Spends credits per size.
generate
export_banners
Packages a campaign for a platform and returns signed download links (1 hour).
export
get_export
Status of an export and, if it is ready, a fresh download link.
export
get_credit_balance
Balance, plan, renewal and the cost of each operation per model.
read

The typical flow is generate_banner → get_job until it finishes → preview_banner → edit_banner or add_sizes → export_banners → share the download link. That is 10 tools; the read-only ones are marked as such for the client.

The rules are the app's

  • If the workspace requires approval before exporting, or the destination URL (clickTag) is missing, the tool says so and does not export.
  • confirm_unapproved (export unapproved pieces, with a watermark) only works if you connected through OAuth with the Admin or Owner role; with an API key it always gives forbidden.
  • Errors come back as text for the assistant: a hint, the code in brackets and the server's message.
  • Every call counts toward the limit of 60 requests per minute. [PLACEHOLDER: confirm the value in production]
Opmerking. Plans that include the MCP server: [PLACEHOLDER: to be confirmed]. The REST API and webhooks are on Team, Agency and Enterprise.
Was deze pagina nuttig?