> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.bannerify.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an MCP client

> Use Bannerify from Claude, Cursor, and other MCP clients.

Bannerify runs a Model Context Protocol (MCP) server at `https://api.bannerify.co/mcp`. Add it to your assistant, and you can list your templates and generate images and PDFs from the chat, with no API key.

## Before you start

* A Bannerify account with at least one template.
* An MCP client that supports remote servers over HTTP, such as Claude Code, Claude Desktop, or Cursor.

## Add the server

Add a remote MCP server with this URL:

```text theme={null}
https://api.bannerify.co/mcp
```

Claude Code:

```bash theme={null}
claude mcp add --transport http bannerify https://api.bannerify.co/mcp
```

Claude Desktop and Cursor read a JSON file with the same shape:

```json theme={null}
{
  "mcpServers": {
    "bannerify": {
      "type": "http",
      "url": "https://api.bannerify.co/mcp"
    }
  }
}
```

VS Code uses a `servers` block:

```json theme={null}
{
  "servers": {
    "bannerify": {
      "type": "http",
      "url": "https://api.bannerify.co/mcp"
    }
  }
}
```

## Sign in and approve

The first time you use the server, your browser opens the Bannerify sign-in page.

Sign in, select the workspace that holds your templates, and allow access.

That is the whole setup. There is no key to create and no token to copy. The assistant signs in again on its own when its session expires.

## Ask for a file

Give the assistant a plain request:

```text theme={null}
List my Bannerify templates and their layers.
```

```text theme={null}
Create a PNG from tpl_lifecycle with the headline "Welcome back, An" and the qr layer set to https://example.com/restart.
```

The assistant picks the tools it needs from [MCP tools](/mcp/tools): it reads your templates, renders the file, and shows you the result.

## Usage and limits

Every generation from an MCP client counts against the same monthly and daily quota as the REST API and the SDKs. The plan of the workspace applies. See [Quota and limits](/account/quota) for the limits of each plan.

## End a connection

Remove the server from your MCP client. The assistant loses access as soon as the client stops using it.

## Troubleshoot

| Symptom | Fix |
| - | - |
| The browser does not open the sign-in page | Use a client that supports remote MCP servers over HTTP |
| The assistant asks you to sign in again | Sign in and allow access again |
| The assistant sees no templates | Connect again and select the workspace that holds your templates |
| The assistant cannot generate a file | Check [Quota and limits](/account/quota) |

## Learn more

* [MCP tools](/mcp/tools)
* [API authentication](/api-reference/authentication)
* [Generate from the terminal](/cli/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.