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

# Kombai Connector

> Add Kombai to Claude, ChatGPT, Figma, or another app that supports remote MCP servers, and ask Kombai's taste agent for design directions from a chat.

The Kombai connector is a remote MCP server that lets apps such as Claude, ChatGPT, and Figma run Kombai's taste agent from a chat. Describe what you're designing, and Kombai writes distinct design directions for it, each with a concept, layout, palette, typography, motion, and links to stock photos and AI images.

> [!NOTE]
>
> The connector writes design directions. It doesn't build designs on a Kombai canvas. To design on a canvas from a coding agent such as Claude Code, Codex, or Cursor, install the [Kombai plugin](https://docs.kombai.com/features/mcp/agent-plugins.md).

## Before you begin

You need an app that supports remote MCP servers with OAuth sign-in, and a Kombai account with credits. You can create an account when you connect, and new accounts start with free credits. See [Credits](https://docs.kombai.com/account/credits.md).

The connector's URL is:

```text theme={null}
https://agent.kombai.com/mcp
```

## Add the connector

> [tab] Claude
>
> Works on claude.ai and in the Claude desktop and mobile apps. On the Free plan, Claude allows one custom connector.
>
> 1. Go to **Customize > Connectors**, select **+ Add**, then **Add custom connector**.
> 2. Enter `Kombai` as the name and `https://agent.kombai.com/mcp` as the URL, then select **Continue**.
> 3. Keep the authentication settings Claude detects, select **Continue** and then **Add**, and [sign in](#sign-in).
>
> On Team and Enterprise, an Owner adds the connector first in **Organization settings > Connectors** (**Add > Custom > Web**), and each member then selects **Connect** on Kombai in **Customize > Connectors**.
>
> To use it in a chat, select **+** in the message box, choose **Connectors**, and turn Kombai on.

> [tab] ChatGPT
>
> A taste run needs ChatGPT's full MCP support: Business, Enterprise, and Edu workspaces, on the web. On Pro, custom MCP servers are read-only, so they can't start a run. On Business, an admin or owner adds the connector.
>
> 1. Go to **Plugins**, select the plus button, then **Add custom MCP server**.
> 2. Enter `Kombai` as the name and `https://agent.kombai.com/mcp` as the server URL, and choose **OAuth**.
> 3. Select **I understand and want to continue**, then **Create as a plugin**, and install it.
> 4. [Sign in](#sign-in) when ChatGPT asks.
>
> To use it in a chat, type `@` and select Kombai. To share it with the workspace, an admin or owner publishes the plugin. See OpenAI's [Connecting custom MCP servers in ChatGPT](https://help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt).

> [tab] Figma
>
> Works in Figma Make and the Figma agent, on Professional, Education (not K-12), Organization, and Enterprise plans. On Organization and Enterprise, only admins can create custom connectors unless an admin allows everyone to.
>
> 1. In the chat's prompt box, open **Add context**, hover over **Connectors**, and choose **Manage**.
> 2. On the **Created by you** tab, select **Create**.
> 3. Enter `Kombai` as the **Name** and `https://agent.kombai.com/mcp` as the **MCP server URL**, leave **Advanced settings** empty, and select **Create**.
> 4. Select **Connect** and [sign in](#sign-in).
> 5. Turn on Kombai's tools. Figma turns off tools that write by default, and `taste_start` counts as one because it starts a run.
>
> To use it in a chat, type `@` and choose Kombai. Figma asks before each tool call, so select **Run** when it does.

> [tab] Coding agents
>
> In a coding agent, the [Kombai plugin](https://docs.kombai.com/features/mcp/agent-plugins.md) does more: it builds designs on a canvas from your brief and your repo. Add the connector only if you want design directions alone.
>
> ```bash Claude Code theme={null}
> claude mcp add --transport http --scope user kombai https://agent.kombai.com/mcp
> ```
>
> ```bash Codex theme={null}
> codex mcp add kombai --url https://agent.kombai.com/mcp
> codex mcp login kombai
> ```
>
> ```json Cursor (~/.cursor/mcp.json) theme={null}
> {
>   "mcpServers": {
>     "kombai": {
>       "url": "https://agent.kombai.com/mcp"
>     }
>   }
> }
> ```
>
> ```json VS Code (.vscode/mcp.json) theme={null}
> {
>   "servers": {
>     "kombai": {
>       "type": "http",
>       "url": "https://agent.kombai.com/mcp"
>     }
>   }
> }
> ```
>
> Then sign in:
>
> * **Claude Code:** run `/mcp` and sign in to `kombai`.
> * **Codex:** `codex mcp login kombai` opens the sign-in in your browser.
> * **Cursor:** in **Cursor Settings > Tools & MCPs**, select **Connect** when `kombai` shows **Needs authentication**.
> * **VS Code:** allow it when VS Code says `kombai` wants to authenticate, or select **Authenticate** when chat asks.

> [tab] Other apps
>
> Any app that supports remote MCP servers over streamable HTTP with OAuth can use the connector. Add `https://agent.kombai.com/mcp`, choose OAuth if the app asks, and sign in.
>
> | App | Where to add it |
> | - | - |
> | Lovable | **Connectors > Add custom > MCP server**. Keep **OAuth (default)** and select **Add & authorize**. |
> | v0 | **+** in the prompt box **> MCPs**, then a custom server with **OAuth**. |
> | Bolt | **+** in the chat box **> Connectors > Manage connectors > Custom MCP server**, with **HTTP** and **MCP OAuth**, then **Connect**. |
> | Replit | **Settings > Integrations > Your integrations > Add custom > Add personal MCP server**, then **Test & save**. |
> | Perplexity | **Plugins > Add custom > Add MCP connector > Remote**, with **OAuth** and **Streamable HTTP** under **Advanced**. Then select the connector card to sign in. In an organization, an admin must first allow members to add custom connectors. |

To check the connection, ask your app how many Kombai credits you have. It answers with your account's email, plan, and credits left.

## Sign in

Your app opens Kombai's sign-in page in your browser. Sign in or create an account, approve the connection, and your app returns to the chat connected. It never sees your Kombai password.

If you sign up with an email and password, confirm your email. Confirming in the same browser finishes the connection. If you confirm on another device, go back to the tab that says **Email confirmed** and select **Continue here**.

To disconnect, remove the Kombai connector in your app.

## Ask for design directions

Mention Kombai and describe what you're designing:

```text theme={null}
Use Kombai to come up with design directions for a landing page for a hiking club in Leeds. It's for people who are new to hiking, and it should feel friendly and outdoorsy.
```

A good brief names the product and the page or screen, who it's for, what it must say or do, the feel you want, and any brand colors, fonts, or constraints to keep. A brief can be up to 8,000 characters.

Your app starts a taste run and gives you a link to its taste card. The run takes a few minutes. When it finishes, apps that show MCP Apps, such as Claude, show the directions as taste cards in the chat; other apps summarize them and give you the link. Ask for a direction by number to get it in full.

You can ask for 1 to 4 directions (the default is 2), and for stock photos only, with no AI-generated images. Each run spends credits, and more directions and AI images spend more. The taste card link opens only for the Kombai account that started the run, and Kombai keeps each run for 30 days.

## Connector tools

Your app calls these tools for you.

| Tool | What it does |
| - | - |
| `taste_start` | Starts a taste run on a brief. Spends credits. |
| `taste_wait` | Waits up to about 20 seconds for a run, and returns an overview of its directions once it has finished. |
| `taste_direction` | Returns one direction in full, with links to its images. |
| `taste_card` | Shows a finished run as taste cards, in apps that show MCP Apps. |
| `kombai_account` | Returns the account's email, plan, and credits left. Read-only. |

## Data and privacy

Kombai receives only the brief your app writes for each run and the options it picks, not the rest of your conversation. Your app signs in with OAuth, and runs belong to your Kombai account and spend its credits.

## Troubleshooting

> [accordion] This Kombai account is out of credits
>
> Open the plan page link your app gives you to get more credits, or see [Credits](https://docs.kombai.com/account/credits.md) for when free credits renew. On a team, your Team Admin adds credits.

> [accordion] As its team's Billing Admin, this account cannot start taste runs
>
> A Billing Admin can't spend the team's credits. Connect with a Team Admin or Team Member account. See [Roles and permissions](https://docs.kombai.com/kombai-for-teams/get-started/roles-and-permissions.md).

> [accordion] Kombai is still setting up this new account's free credits
>
> Ask your app to try again in a minute.

> [accordion] This Kombai account's email address cannot be used to start taste runs
>
> Kombai doesn't run taste for some addresses, such as disposable ones. Disconnect and connect again with an account that uses another email address, or contact [support@kombai.com](mailto:support@kombai.com).

> [accordion] The sign-in page says “You're signed in” and asks you to connect again
>
> The connection request expired while you were signing in. Go back to your app and connect again. You're already signed in, so it goes straight through.

> [accordion] The directions don't appear as cards
>
> Your app doesn't show MCP Apps in this chat. Open the taste card link it gives you instead.

> [accordion] Claude can't find Kombai's tools after you added the connector again
>
> A chat opened before you re-added the connector still points at the old one. Reload the chat or start a new one.


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