# Kite MCP server

> Design screens, sites and brands in a canvas where agents and people edit the same HTML and CSS files.

- Listing: https://mcp.tc/i/kite
- Connect: use the server's own URL `https://kite.new/api/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Design, Websites & CMS](https://mcp.tc/c/design)
- Vendor: Kite
- Homepage: <https://kite.new/>

## About

Kite is a design canvas built for agents and humans. Through its MCP server, an assistant can read, draw, edit and check designs, working from the workspace's design system (variables, components and skills) and answering comments on frames.

The hosted endpoint uses streamable HTTP and works with MCP clients that support OAuth, such as Claude, Cursor, ChatGPT and Codex. Users sign in through the browser, and no API key needs to be copied. Kite for Mac also adds a local server.

## What it can do

- Read and inspect design files
- Draw and edit screens as HTML and CSS
- Use design system variables and components
- Answer comments pinned on frames
- Check designs after editing

## Example prompts

- "Design a home page hero for Lumen using our design system."
- "Add a Pay button under the balance on the Checkout frame."
- "Do my Kite requests."
- "Make a phone version of this screen."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http kite https://kite.new/api/mcp
```

2. Start Claude Code, type `/mcp`, pick **kite** and choose **Authenticate**. A browser window opens for the Kite sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Kite** and paste this URL:

```url
https://kite.new/api/mcp
```

3. Click **Add**, then **Connect**, and sign in when Kite asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Kite&connectorUrl=https%3A%2F%2Fkite.new%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://kite.new/api/mcp` and click **Add**.

3. Click **Connect** and sign in when Kite asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://kite.new/api/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Kite to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=kite&config=eyJ1cmwiOiJodHRwczovL2tpdGUubmV3L2FwaS9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "kite": {
      "url": "https://kite.new/api/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=kite&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fkite.new%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"kite","type":"http","url":"https://kite.new/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "kite": {
      "type": "http",
      "url": "https://kite.new/api/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "kite": {
      "serverUrl": "https://kite.new/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add kite --url https://kite.new/api/mcp
codex mcp login kite
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.kite]
url = "https://kite.new/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http kite https://kite.new/api/mcp
```

Then, inside Gemini CLI, run `/mcp auth kite` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "kite": {
      "type": "http",
      "url": "https://kite.new/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://kite.new/api/mcp`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-07
- Updated: 2026-11-07

---
Source: https://mcp.tc/i/kite (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
