> ## 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 MCP Server

> Let coding agents like Claude Code, Cursor, and Codex start Kombai chats and read your canvases from outside the app.

Once your client is connected to Kombai, it can start a Kombai chat in a named workspace folder, follow a running chat and read its result, and read the designs on a canvas.

## Open the server settings

Click the <Icon icon="gear" size={18} /> icon in the top bar to open the [Settings](/account/settings) page, then select the **Kombai MCP Server** tab.

If the server is running, you will see a **Active** badge with the port it's listening on, above the **Clients** section. If it reads **The MCP bridge is not running**, restart Kombai to bring it back.

<Note>
  The server runs when you are using the Kombai app. There's no separate on/off
  switch for it. Turning a client on or off only changes that client's
  configuration.
</Note>

## Supported clients

Kombai detects these clients and writes its entry into each one's own user-level configuration file:

| Client                 | Configuration file                                  |
| ---------------------- | --------------------------------------------------- |
| **VS Code / Insiders** | `Code/User/mcp.json` in your VS Code user directory |
| **Cursor**             | `~/.cursor/mcp.json`                                |
| **Claude Code**        | `~/.claude.json`                                    |
| **Codex**              | `~/.codex/config.toml`                              |
| **Antigravity**        | `~/.gemini/antigravity/mcp_config.json`             |
| **Gemini CLI**         | `~/.gemini/settings.json`                           |

Kombai shows a **Detected** badge for each client it finds on your machine, and a **Not Installed** badge for those it doesn't. If your client isn't detected, install it first, then restart Kombai to detect it.

You can also connect a client manually if it's not listed above. To do so, copy the **Manual configuration** snippet from below the **Clients** section into your client's own MCP configuration. To use the skills there as well, place each skill's `SKILL.md` at `<skill-name>/SKILL.md` in that client's skills folder.

## Connect a client

<Steps>
  <Step title="Turn the client on">
    Toggle a detected client on. Kombai adds itself to that client's MCP configuration and installs the Kombai skills into the client's skills folder.
  </Step>

  <Step title="Use a skill from the client">
    In the client, type the skill you want to use. For example, `/design-with-kombai` to hand that task to Kombai.
  </Step>
</Steps>

<Note>
  Toggling the client off removes both the configuration entry and the skills.
</Note>

## Installed skills

Kombai installs a set of skills into each client it connects to. These skills let the client hand tasks to Kombai and read the results back. Each skill is a folder with a `SKILL.md` file that describes what it does and how to use it.

| Skill                    | What it does                                                  |
| ------------------------ | ------------------------------------------------------------- |
| `design-with-kombai`     | Hand a UI design task to Kombai, built on its canvas.         |
| `code-with-kombai`       | Have Kombai implement a coding task in the current workspace. |
| `code-kombai-design`     | Turn a design from a Kombai canvas into code.                 |
| `improve-ui-with-kombai` | Ask Kombai to polish or rework existing UI.                   |
| `review-ui-with-kombai`  | Get a read-only UI and UX critique from Kombai.               |
| `describe-kombai-canvas` | List and describe the designs on your Kombai canvases.        |
| `kombai-faq`             | What Kombai can do and how to use it from this agent.         |