Bannerbear MCP integration for AI agents.
Connect AI agents to Bannerbear through 5 structured actions, including get auth, create image sync, and get image. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bannerbear integration exposes
The Bannerbear Agent App exposes 5 provider-backed actions for design & media and marketing work. Its current contract lets an authorized agent verify a bannerbear api key and return the project it is scoped to, create a bannerbear image synchronously from a template and return the generated media urls, and retrieve one bannerbear image by uid. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bannerbear account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bannerbear capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_authREADVerify a Bannerbear API key and return the project it is scoped to.
INPUTS: project_id
create_image_syncWRITECreate a Bannerbear image synchronously from a template and return the generated media URLs.
INPUTS: template / modifications / transparent / render_pdf / metadata
get_imageREADRetrieve one Bannerbear image by UID.
INPUTS: uid / project_id
get_templateREADRetrieve one Bannerbear template by UID.
INPUTS: uid / extended / project_id
list_templatesREADList Bannerbear templates in the connected project.
INPUTS: page / limit / tag / name / extended
INPUT CONTRACTS
Know what the action needs before it runs.
get_auth
project_idOPTIONAL- The Bannerbear project UID. Required when using a Full Access Master API Key.
create_image_sync
templateREQUIRED- The template UID to use.
modificationsREQUIRED- Template layer modifications to apply.
transparentOPTIONAL- Whether to render a transparent PNG.
render_pdfOPTIONAL- Whether to also render a PDF.
metadataOPTIONAL- Custom metadata to store with the generated image.
get_image
uidREQUIRED- The Bannerbear resource UID.
project_idOPTIONAL- The Bannerbear project UID. Required when using a Full Access Master API Key.
get_template
uidREQUIRED- The Bannerbear resource UID.
extendedOPTIONAL- Whether to include current layer defaults.
project_idOPTIONAL- The Bannerbear project UID. Required when using a Full Access Master API Key.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Auth
Verify a Bannerbear API key and return the project it is scoped to. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_authControl Create Image Sync
Create a Bannerbear image synchronously from a template and return the generated media URLs. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_image_syncVerify with Get Image
Retrieve one Bannerbear image by UID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_imageSAFETY BOUNDARY
Operate Bannerbear with explicit limits
- Authorize Bannerbear with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bannerbear rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bannerbear task completed successfully.
CONNECTION MODEL
API key
Bannerbear Project API Key or Full Access Master API Key sent as an Authorization Bearer token. Find Project API Keys in Project Settings or manage Master API Keys at https://app.bannerbear.com/account/api_keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bannerbear.