Skip to main content
The Bannerify MCP server has six tools. The assistant picks them from your request, so you rarely call one by name. Every tool works only on the workspace of the connection. Connect an MCP client first if you have not.

Tools

Use a template id exactly as list_templates returns it.

Find a template

Ask for the templates and their layers:
The tool returns one entry for each template. Without includeLayers, an entry holds only the id and the name. With it, each layer comes with the name to use in modifications:
suggestInput names the field to set: text for a text layer, src for an image layer, and null for every other type. A layer without a name shows as Untitled. Layer names come from the template editor, where you rename a layer by double-clicking it. Modifications explains how a name matches a layer.

Pass layer values

modifications is an object keyed by layer name. A string sets the text of the layer, and an object sets the fields of that layer. The array format of the REST API is not valid here. A full example for create_image:
A layer that you leave out keeps the values from the template, and a name that matches no layer is ignored. Modifications lists the fields of every layer type.

Read the result

create_image returns the image inline, with a line that gives its format and size in bytes. Your client decides how to show or save the image. create_pdf stores the file and returns a link:
The PDF has one page with the size of the canvas, and its text can be selected and searched. Generate PDFs has the details.

Compose an image without a template

Use create_image_from_shapes when no template fits. Give the tool a canvas and a list of shapes. It draws the shapes in order and returns the image, so the assistant can design a one-off banner or invoice. The canvas object is optional. It is 1200 by 630 pixels and white unless you set these fields: Every shape has type, x, y, width, and height, in pixels from the top left of the canvas. The first shape is at the back and the last is on top. Three more fields work on every type: opacity (0 to 1), rotation (degrees, clockwise), and style. A few rules:
  • icon takes an Iconoir name, for example check-circle or arrow-right. A name that Iconoir does not have fails the call.
  • src takes an HTTPS URL or a data URL. A remote image loads with the same rules as in a template: PNG, JPEG, WebP, or SVG, and a failed download returns FETCH_IMAGE_ERROR.
  • A table has one value per column in every row. This differs from modifications, where a row is an object. variant is line, grid (default), minimal, striped, compact, bordered, or primary-header.
  • style takes CSS property names in camelCase, for example padding, boxShadow, lineHeight, and letterSpacing. A key that the renderer does not support fails the call with an Unrecognized key message. Set the size with width and height, not with style.
  • A field on the shape, such as color or borderRadius, wins over the same key in style.
  • A color is a hex value, rgb(), hsl(), or a CSS color name.
A full example, an invoice:
Bannerify checks the whole request before it renders, so an invalid request does not use a generation. A valid one counts like a generation from a template. See Quota and limits.

Handle errors

A failed call returns isError: true and a text message in one of two forms: A missing or expired token gets HTTP 401 with the error invalid_token before any tool runs, so a tool never returns UNAUTHORIZED. Your client then signs in again. RATE_LIMITED and TOO_MANY_REQUESTS do not occur, because the MCP server has no request rate limit. Handle errors lists the codes of the REST API.

Learn more