https://api.bannerify.co/mcp. This page is for anyone who works with an AI assistant, such as Claude, Cursor, or VS Code, and wants it to use their Bannerify templates. Once the server is connected, the assistant can:
- List your templates and the layers you can change in each one.
- Generate an image or a PDF from a template.
- Compose a one-off image from shapes when no template fits.
Before you start
- A Bannerify account. The template tools need at least one template, and composing an image from shapes needs none.
- An MCP client that supports remote servers over HTTP and OAuth sign-in.
Add the server
The server URL ishttps://api.bannerify.co/mcp, and it uses the Streamable HTTP transport. The Agents & MCP page in the dashboard shows the same setup steps for each client, with buttons to copy the URL and the commands.

The Agents & MCP page in the dashboard.
- Claude Code
- Claude
- Cursor
- VS Code
- Codex
Add the server, then start the sign-in from inside Claude Code:Run
/mcp in Claude Code and follow the steps in your browser.To share the server with your team, put a .mcp.json file at the root of your project:Sign in
The first time your client connects, it has no token, so Bannerify sends it to the sign-in page. Your client opens that page in a browser. After you sign in, you choose the workspace that the client can use. The client keeps the token and sends it with each request. You create no API key and copy no token. The exchange works in four steps:- The client sends a request to
https://api.bannerify.co/mcpwith no token. The server answers with HTTP 401 and aWWW-Authenticateheader that points to its metadata athttps://api.bannerify.co/.well-known/oauth-protected-resource/mcp. - The metadata names the sign-in service, and the client sends you there.
- You sign in to Bannerify. The consent page shows the name of the client and where it sends the token. Choose your Personal workspace or a team workspace, then click Allow.
- The client receives an access token and sends it as
Authorization: Bearer <token>with each request. Bannerify checks that the token is valid, has not expired, and was issued for the MCP URL.
Ask for a file
Give the assistant a plain request:Usage and limits
A generation from an MCP client counts toward the same monthly and daily limits as the REST API and the SDKs. The plan of the connected workspace applies.
A render that fails does not count. A team workspace on the Free plan cannot generate files, and a new team workspace starts with a 14-day Automate 3k trial. The MCP server has no request rate limit. Quota and limits has the limit of each plan.