# Kite

> Kite (https://kite.new) is an AI design tool where your agents and your team design on one canvas. Claude, ChatGPT, Cursor, Codex or any MCP client draws in a Kite design file while the team watches, follows the file's design system and takes jobs from comments. A design is real HTML and CSS. There are no AI credits: agents run on the plan the user already pays for.

Kite here is the design tool at kite.new, not Zerodha's Kite trading API or the Kite AI blockchain project.

This is the full version of https://kite.new/llms.txt: what Kite does, its plans, how agents connect, every MCP tool, how it compares with other design tools and where each doc is.

## What Kite is

**What is Kite?** Kite is an AI design tool where your agents and your team design on one canvas. Claude, ChatGPT, Cursor or any MCP client draws in your file while you watch, follows your design system and takes jobs from comments.

**Is Kite a Figma alternative?** Yes. Kite has what you reach for in Figma: auto layout, components with variants, variables with modes, a pen tool and real type. It pastes to and from Figma and imports whole Figma files. And a design is real HTML and CSS, so agents design in it directly.

**Can Claude design in Kite?** Yes. Add Kite from Claude's connector directory in one click, or connect Claude Code with one command. Claude then makes files, draws in them while you watch and answers your team's comments. ChatGPT, Cursor, Codex and other agents connect the same way.

**Does Kite have an MCP server?** Yes. Kite's hosted MCP server works with any client that supports streamable HTTP and OAuth, with 59 tools to read, draw, edit and check designs. Kite for Mac adds a local one for agents on your machine.

**How much does Kite cost?** Kite is free to start, with unlimited editors and viewers, and 3 files. Pro is $20 per editor a month, or $16 billed yearly. There are no AI credits: your agent runs on the plan you already pay for.

## Features

- **What a design is:** Real HTML and CSS, the language agents already read and write
- **Big files:** Smooth on a 19,600-layer page: frames far off screen are drawn as pictures
- **Vector editing:** Pen tool, point editing and boolean operations
- **Components:** Components with variants, properties and instance swap
- **Variables:** Variables with modes, like light and dark, set per frame
- **Auto layout:** Rows, columns and grids that grow with their content
- **Hosted MCP server:** Any agent connects from anywhere, signing in with OAuth
- **Local MCP server:** Built into Kite for Mac, for agents on your machine
- **What agents can do:** 59 tools: agents read, draw, edit and check their own work
- **Which agents:** Claude, ChatGPT, Cursor, Codex or any MCP client
- **Jobs from comments:** @-mention an agent in a comment and it makes the change
- **Several agents at once:** Several agents in one file, beside your team
- **Agent limits:** 200 agent actions a day on Free; unlimited on Pro
- **AI credits:** None: your agent runs on the plan you already pay for
- **Where files live:** In the cloud, open in any browser or in Kite for Mac
- **Version history:** Autosaves every 10 minutes, plus named versions to go back to
- **Export:** PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind
- **Figma:** Paste to and from Figma, or import a whole file by its link
- **Live cursors:** Live cursors and selections for everyone in the file
- **Comments:** Comment threads pinned to the design, with email notifications
- **Workspaces and roles:** Workspaces with owner, editor and viewer roles
- **Share links:** One link per file, and guests comment with just a name
- **Custom fonts:** Upload your own, or use any Google font
- **Browser extension:** Kite Capture copies any web page into Kite as layers
- **Desktop app:** Kite for Mac and Windows, with a tab for each file
- **Free plan:** Unlimited editors and viewers, and 3 files, free

## Plans and pricing

- **Free:** unlimited editors and viewers, one workspace of your own with 3 files, and 200 agent actions a day, with everything in the editor and any agent.
- **Pro:** $20 per editor a month, or $16 a month billed yearly. Unlimited files and agent actions, and version history.
- **Team:** $35 per editor a month ($28 billed yearly). Everything in Pro, plus SSO and SAML, admin controls, custom contracts and dedicated support.

**Is Kite free?** Yes. The free plan has unlimited editors and viewers, a workspace of your own with 3 files, and 200 agent actions a day, with everything in the editor and any agent you want to connect.

**Do I pay for AI credits?** No. Kite has no model of its own: your agent runs on the plan you already pay for, like Claude, ChatGPT or Cursor. Kite charges for the people who edit, never for the AI, so you never pay twice.

**Who counts as an editor?** Someone who can change your files, in the workspace or on one file. On Free, invite as many as you like. On Pro each is a paid seat, and you choose who edits in People. Viewers are free on every plan, and guests can comment on a shared file with just a name.

**What does Team add?** Everything in Pro, plus SSO and SAML, admin controls, custom contracts and dedicated support. Write to hello@kite.new to set it up.

Details: https://kite.new/pricing

## For agents: connecting to Kite

- **Hosted MCP server:** https://kite.new/api/mcp (Streamable HTTP). Sign-in: OAuth 2.1 with PKCE and dynamic client registration (https://kite.new/auth.md), or an API key the user makes at https://kite.new/settings?tab=agents.
- **Claude:** one click from the connector directory, https://claude.ai/directory/connectors/kite.
- **Kite for Mac:** a local MCP server (`~/.kite/bin/kite mcp`) for agents on the user's machine, which sees the files they have open.
- **Clients with setup guides:** https://kite.new/docs/mcp/clients (Claude, Claude Code, ChatGPT, Codex, Cursor, VS Code, GitHub Copilot CLI, Grok, Manus, v0, Antigravity, Muse and any other MCP client).
- **How to work in a file:** https://kite.new/skill.md. Machine-readable: https://kite.new/.well-known/mcp/server-card.json.

## MCP tools (59)

- **guide_read** (Read the Kite guide): How to work in Kite, by topic: "drawing" (writing layers, checking them with layer_render, stopping), "effects", "components", "design-systems", "comments-and-requests" and "files".
- **system_list** (List design systems): The workspace's design systems: variables (colours, type, spacing, radii — in collections with modes such as Light and Dark) and styles (text, effect, colour) that design files use as var(--name).
- **system_read** (Read a design system): A design system in full: its collections and their modes; every variable with its type, its value in each mode (an alias by its target's name), its css and what it is for; its styles and the var() of each part; the same as CSS; how to use them; and its skills — with `file`, the file's own too — each by name and first line.
- **system_new** (Create a design system): Make a design system in the workspace: from collections and variables you send (read from a codebase's CSS variables, a Tailwind config or a design — modes such as Light and Dark as a collection's modes, aliases as { alias: name }), from a preset, or from a website (`from_url`: several of its pages are measured as a visitor sees them — colours by the area they paint, the primary from its most prominent button, its section colour schemes as modes, type by role with case and tracking — its look is read from pictures of them, and its logos, the parts copied off its pages and every picture, drawing and video it shows become a library of components — two to three minutes).
- **system_apply** (Apply a design system): Make a design file use one of the workspace's design systems (by name or id), or none (`system: null`).
- **skill_read** (Read a skill): One skill's instructions, by name: from a file, its own skills and then its design system's; from a design system, its skills.
- **skill_edit** (Edit skills): Add, change or take out skills, by name, when the user asks: what agents should know — a guardrail ("never show prices"), how a kind of design is made here, a voice.
- **file_new** (Create a design file): Start a project: one file, a canvas where the visual assets you make for the user are kept — banners, social posts, ads, logos, icons, identity boards — so they are saved and visible side by side.
- **variable_edit** (Edit design variables): Change a design system's variables, by name: make or change collections and their modes (Light, Dark…), make or change variables — a value for every mode, or one per mode by its name, an alias as { alias: "name" } — and take any out (an alias to one taken out keeps the value it gave).
- **style_edit** (Edit design styles): Change a design system's styles, by name: make or change text, effect, colour and grid styles — each part a CSS value or an alias to a variable ({ alias: "font/heading" }), null to take a part out — and take styles out.
- **file_list** (List design files): List your projects (design files) and the ones shared with you, newest edit first.
- **file_info** (Get file details): Get a project's details: title, URL, audience, comment count.
- **file_share** (Change who can open a file): Change who can open a project: 'link' (anyone with the link) or 'restricted' (only the emails listed, which replace the list).
- **comment_list** (List comments): Read comments viewers left on a design file, oldest first.
- **comment_reply** (Reply to a comment): Reply to a comment on your page or a design file you can open.
- **comment_new** (Start a comment): Start a comment thread in a design file you can open, pinned where it is about: on a layer (`layer`, from file_outline or layer_search: the pin goes on it, in its frame), or on a spot of the empty board (`board`: a page and board x, y).
- **request_list** (List requests for agents): Requests people left for you in comments by naming you — "@Claude make this card denser" — across their design files, or one file's, oldest first.
- **file_archive** (Archive a file): Archive one of your projects.
- **file_edit** (Change a file): Change a design file you can edit: its name (`title`), the folder it is in (`folder`, by name or id, of its workspace; null for none) or its thumbnail in the library (`thumbnail`: a top-level frame's id; null for the first page's front frame).
- **file_copy** (Copy a file): Copy a design file you can edit, with every page, layer and picture in it: a new private file beside it (or in the person's own workspace when they can't add files to its one).
- **file_unarchive** (Unarchive a file): Bring back a design file from the Archive (file_archive put it there, or a person did): its link works again and it is back in the library.
- **file_search** (Search design files): Find your projects by what is in them, not just their title: the search covers their pages, their layers' names and the words in them.
- **file_outline** (Read a file's outline): Read a design file (one made by file_new): its pages and, for one page, the outline of every node — frames, text, images, SVGs — with ids, sizes and board positions, and a picture's own size and whether it is see-through where Kite knows them.
- **editor_focus** (See what's open and selected): What the person has open and selected in the Kite editor — the file they're looking at and the layers they mean when they say "this", "these" or "the selected card" — with an outline of each (ids, sizes, text) and the frame each is in.
- **picture_add** (Add a picture): Put a picture file into a design file: a PNG, JPEG, GIF or WebP, as base64 (a data: URL works too).
- **video_add** (Add a video): Put a video into a design file: an MP4, WebM or MOV up to 100 MB, sent as it is — never turn a video into a GIF or a still to put it in.
- **font_lookup** (Look up fonts): Check fonts before you style text: for each family, whether Kite has it (the workspace's own uploaded fonts, every Google Fonts family, and the system's), and the styles it really has — weight, italic and name — and its variable axes.
- **font_add** (Add a font): Put a font file into the workspace of a design file, for every file in it: a TTF, OTF, WOFF or WOFF2 up to 4 MB, as base64 (a data: URL works too).
- **layer_render** (Render a preview): See a node as the person sees it: a PNG of a frame (or any node) rendered with its fonts and pictures.
- **layer_search** (Search layers): Find nodes in a design file by name or by the words in them (case-insensitive), optionally only of one type.
- **layer_copy** (Copy layers): Copy nodes with everything inside them.
- **layer_send** (Send layers to another file): Copy layers from one design file into another (`to_file`), with everything inside them: set down on a page of it (`page`, by name or id, made if new; else its first) at x, y, or to the right of what is there.
- **layer_export** (Export a layer): A layer as a file you can use elsewhere, in the answer: `svg` (drawn as the person sees it, its words as text and its fonts and pictures inside), or code — `react` (JSX with style objects; a component with its properties, an instance as the element placing it), `tailwind`, or `html` — with the design system's variables it uses written out as CSS.
- **web_capture** (Bring in a web page): Bring a web page into a design file as layers you can edit, as Kite Capture does for a person: the whole page as a desktop browser shows it (1440 px wide), its pictures kept in the file and its own fonts added to the workspace.
- **component_make** (Make a component): Make a node a main component (as ⌥⌘K does in the editor): its instances then follow every change made to it, except what an instance changes for itself.
- **component_place** (Place a component): Place an instance of a main component or a component set (its default variant; pass `properties` to choose another, and to set its other properties): a copy that follows the main.
- **component_combine** (Combine as variants): Combine main components into a component set, as Figma's Combine as variants: each becomes a variant, its name its values.
- **component_properties** (Component properties): Add, rename, remove and set the defaults of a component's properties — on a component set, or a main not in a set — and tie layers inside it to them, as Figma's Properties panel.
- **instance_set** (Set instance properties): Set an instance's component properties by name, as the instance panel does: a variant property switches it to that variant (the closest if none has every value asked for), a boolean shows or hides, a text sets the words, a swap takes a component id.
- **library_list** (List libraries): The libraries a design file can use — other files of its workspace whose components are published for the rest — each with its components and component sets: place one with component_place { component, library }, a set by its id with `properties` choosing the variant.
- **library_publish** (Publish a library): Publish a design file's main components as a library, so the other files of its workspace can place them (component_place { library }); called again, it publishes what changed since, and files using them see the update waiting.
- **library_update** (Update library components): Bring a design file's instances of library components up to the libraries' latest versions (library_list says which are waiting): every value an instance has not made its own takes the library's, as one step the person can undo.
- **component_detach** (Detach an instance): Make an instance an ordinary group of layers again: it stops following its main component.
- **layer_source** (Read a layer's HTML): The HTML of a node and everything in it (or of a whole page), with every style inline and each element's node id in data-id; `pictures`: each picture it shows, with its own width and height and whether it is see-through (`transparent`), where Kite knows them.
- **layer_draw** (Draw layers): Draw into a design file by writing HTML.
- **layer_edit** (Edit layers): Change nodes in place: CSS (kebab-case properties; null removes one), a text's words, a name, a top-level frame's board position, visibility or lock.
- **layer_nest** (Move layers): Move nodes into another node (or onto the board with parent: null), at an index among its children.
- **layer_remove** (Remove layers): Delete nodes and everything inside them.
- **page_new** (Add a page): Add a page to a design file, after the others or at `index` in the list, with its icon and the icon's colour in the page list.
- **page_edit** (Change a page): Change a page of a design file: its name, its icon and the icon's colour in the page list (null takes them off), its canvas colour (`background`, a hex; null for the editor's own), or its place in the list (`index`, 0 first).
- **page_copy** (Copy a page): Copy a page of a design file with every layer on it, its icon, canvas colour and guides, as a new page after the others — of the same file, or of another of its workspace (`to_file`), where it keeps its name (numbered if that file has a page of it).
- **page_move** (Move pages to another file): Move pages of a design file, with every layer and comment on them, into another design file of the same workspace (`to_file`), after its own pages.
- **page_merge** (Merge pages): Merge pages of a design file into one: every layer on `pages` moves onto `into`, each page's layers laid out as they were and set to the right of what is there, under the same ids; the emptied pages are then deleted.
- **page_remove** (Delete a page): Delete a page of a design file and every layer on it.
- **version_list** (List versions): A design file's version history, newest first: versions saved by name (by people or agents), and the ones Kite saves on its own as the file changes.
- **version_save** (Save a version): Save a design file as it is now, as a named version in its history (people see it in Version history).
- **version_restore** (Restore a version): Take a design file back to a version from version_list: everything in it becomes as it was then, for everyone with it open.
- **file_settings** (Agent settings of a file): How the person wants agents to work in a design file; pass a value to change it.
- **finish_working** (Finish working): Say you have finished working in a design file, when you are done with what you were asked, even if you couldn't finish: the person sees you stop at once and can edit those frames again.

## Kite compared with other design tools

Each comparison is also a page at https://kite.new/compare/<tool>. The other tools' columns come from their own docs, pricing and changelogs as of October 2026; rows their docs say nothing about are left out.

### Kite vs Figma

Kite is a design tool built on real HTML and CSS, for the agents you already use: Claude, ChatGPT or Cursor design in your file in the language they know, follow your design system and take jobs from comments. Figma keeps designs in its own format, gives outside agents 20 calls a month on free seats, and lets them draw only on paid plans.

Kite is for: Teams whose agents draw part of the design, beside the people.

Why teams pick Kite over Figma:
- Designs are real HTML and CSS. Agents read and write them directly, with nothing to translate from a closed format.
- Free includes 200 agent actions a day, and Pro has no cap. Figma's free seats get 20 calls a month, and can't draw.
- @-mention an agent in a comment and it makes the change.
- No AI credits. Your agent runs on the plan you already pay for.
- Agents read your design system and its rules before they draw.
- Kite for Mac runs agents on your own machine.

| | Kite | Figma |
|---|---|---|
| What a design is | Real HTML and CSS, the language agents already read and write | Its own format, translated to code |
| Vector editing | Pen tool, point editing and boolean operations | Yes |
| Components | Components with variants, properties and instance swap | Yes, with variants |
| Variables | Variables with modes, like light and dark, set per frame | Yes, with modes |
| Auto layout | Rows, columns and grids that grow with their content | Yes |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes |
| Local MCP server | Built into Kite for Mac, for agents on your machine | Yes, in Dev Mode |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Draws in beta, on paid plans |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes, approved clients only |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | 20 calls a month on free seats |
| AI credits | None: your agent runs on the plan you already pay for | Yes, AI credits |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | Yes; branching on Organization |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | PNG, JPG, SVG, PDF, MP4, GIF |
| Live cursors | Live cursors and selections for everyone in the file | Yes |
| Comments | Comment threads pinned to the design, with email notifications | Yes |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Yes |
| Share links | One link per file, and guests comment with just a name | Yes |
| Free plan | Unlimited editors and viewers, and 3 files, free | Yes, 20 MCP calls a month |

**Is Kite a good Figma alternative?** Yes. Kite is a design tool built on real HTML and CSS, for the agents you already use: Claude, ChatGPT or Cursor design in your file in the language they know, follow your design system and take jobs from comments.

**Can I bring my Figma files into Kite?** Yes. Copy frames in Figma and paste them into Kite as layers you can edit, or import a whole file by its link. Copy to Figma sends frames back the other way.

Page: https://kite.new/compare/figma

### Kite vs pen.dev

Kite is a design tool where your team and its agents work in the same file at once, with live cursors, comments and share links that stay live. pen.dev keeps designs as local files, shared as snapshots.

Kite is for: Teams designing and reviewing together, with agents in the same file.

Why teams pick Kite over pen.dev:
- Designs are real HTML and CSS, not a JSON format that has to be translated to code.
- Files live in the cloud, with share links that stay live. pen.dev's files sit on your disk, and its links are snapshots you update by hand.
- A hosted server, so ChatGPT and other agents in the browser can connect. pen.dev's runs only on your machine, with its app open.
- Components with variants.
- Figma both ways. pen.dev imports from Figma but can't send back.
- Version history without setting up git.

| | Kite | pen.dev |
|---|---|---|
| What a design is | Real HTML and CSS, the language agents already read and write | .pen JSON on a WebGL canvas |
| Vector editing | Pen tool, point editing and boolean operations | Pen tool and point editing |
| Components | Components with variants, properties and instance swap | Yes, no variants |
| Variables | Variables with modes, like light and dark, set per frame | Yes, with themes |
| Auto layout | Rows, columns and grids that grow with their content | Flex layout |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | No, local only |
| Local MCP server | Built into Kite for Mac, for agents on your machine | Yes, with the app open |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Yes |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes |
| Several agents at once | Several agents in one file, beside your team | Up to 6 agents, by plan |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | 5 agent-days a month free |
| AI credits | None: your agent runs on the plan you already pay for | Model credits, or your own key |
| Where files live | In the cloud, open in any browser or in Kite for Mac | On your disk |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | Through git |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | PNG, JPG, WebP, PDF, HTML |
| Figma | Paste to and from Figma, or import a whole file by its link | Import only |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Member roles on Pro |
| Share links | One link per file, and guests comment with just a name | Snapshots, updated by hand |
| Custom fonts | Upload your own, or use any Google font | Custom font files |
| Browser extension | Kite Capture copies any web page into Kite as layers | Yes, web import |
| Desktop app | Kite for Mac and Windows, with a tab for each file | Mac, Windows and Linux |
| Free plan | Unlimited editors and viewers, and 3 files, free | 5 agent-days a month, 1 agent |

**Is Kite a good pen.dev alternative?** Yes. Kite is a design tool where your team and its agents work in the same file at once, with live cursors, comments and share links that stay live.

Page: https://kite.new/compare/pen-dev

### Kite vs Penpot

Kite is a design tool your agents reach from anywhere, with nothing to keep open, plus Figma both ways and a desktop app. Penpot is open source and you can host it yourself; its MCP server works through a Penpot browser tab that has to stay open, one tab at a time.

Kite is for: Teams whose agents should connect from anywhere, with Figma both ways and a desktop app.

Why teams pick Kite over Penpot:
- Agents sign in with OAuth and nothing has to stay open. Penpot's MCP runs through a Penpot browser tab that must stay open and awake.
- 59 tools to read, draw, edit and check the work. Penpot's server has five, and agents write through one that runs code.
- Several agents in one file. Penpot's MCP is active in one browser tab at a time.
- Paste to and from Figma, or import a whole file by its link. Penpot imports Figma once, with a plugin.
- Kite for Mac and Windows. Penpot has no official desktop app.

| | Kite | Penpot |
|---|---|---|
| What a design is | Real HTML and CSS, the language agents already read and write | SVG-based, with designs as code-readable data |
| Big files | Smooth on a 19,600-layer page: frames far off screen are drawn as pictures | A faster WebGL renderer, in beta, switched on in settings |
| Vector editing | Pen tool, point editing and boolean operations | Path tool and five boolean operations |
| Components | Components with variants, properties and instance swap | Components with variants |
| Variables | Variables with modes, like light and dark, set per frame | Design tokens with themes, like light and dark |
| Auto layout | Rows, columns and grids that grow with their content | Flex and Grid layout, built on CSS |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes, with a personal key, through a Penpot tab that must stay open |
| Local MCP server | Built into Kite for Mac, for agents on your machine | Yes, run from the terminal |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Five tools; agents write by running code |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Any MCP client, such as Claude, Codex, Cursor or VS Code |
| Several agents at once | Several agents in one file, beside your team | MCP is active in one browser tab at a time |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | No MCP call limits stated |
| AI credits | None: your agent runs on the plan you already pay for | None: no built-in AI credits |
| Where files live | In the cloud, open in any browser or in Kite for Mac | In Penpot's cloud, or on your own servers |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | Autosaved versions, 7 days on free, plus pinned versions |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | PNG, JPEG, WebP, SVG and PDF, with CSS and HTML in Inspect |
| Figma | Paste to and from Figma, or import a whole file by its link | Import once, with the Penpot Exporter plugin |
| Live cursors | Live cursors and selections for everyone in the file | Real-time collaboration |
| Comments | Comment threads pinned to the design, with email notifications | Comments on the canvas, to reply to and resolve |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Teams with owner, admin, editor and viewer roles |
| Share links | One link per file, and guests comment with just a name | Public links to view a prototype |
| Custom fonts | Upload your own, or use any Google font | Google Fonts, or upload your own |
| Desktop app | Kite for Mac and Windows, with a tab for each file | No official app; it runs in the browser |
| Free plan | Unlimited editors and viewers, and 3 files, free | Free for up to 8 team members, unlimited viewers, no file limit |

**Is Kite a good Penpot alternative?** Yes. Kite is a design tool your agents reach from anywhere, with nothing to keep open, plus Figma both ways and a desktop app.

**Is Kite open source like Penpot?** No. Kite is a hosted product, and you can't run it on your own servers. If open source or self-hosting is a must, Penpot is the better pick.

**Do Kite and Penpot both work with Claude and Cursor?** Yes, both have MCP servers. Penpot's hosted server signs in with a personal key in its address, and works through a Penpot browser tab that has to stay open and awake, one tab at a time. Kite's signs in with OAuth and needs nothing open, and several agents can work in one file.

**Does Penpot charge for AI?** No. Penpot has no built-in AI credits, and its MCP server is free. Kite has no AI credits either: with both, your agent runs on the plan you already pay for.

Page: https://kite.new/compare/penpot

### Kite vs Wonder

Kite has no built-in AI to pay for: the agents you already use design in it, with a full vector editor, and take jobs from comments. Wonder sells its own AI chat, with $20 of AI tokens a seat each month.

Kite is for: Teams that already pay for Claude, ChatGPT or Cursor and want them designing.

Why teams pick Kite over Wonder:
- No AI tokens to buy: Kite has no model of its own, so you never pay twice for AI.
- Vector editing with a pen tool and points. Wonder's vectors are AI-made SVGs you can't reshape on the canvas.
- @-mention an agent in a comment and it makes the change.
- A local server in Kite for Mac, so agents on your machine connect directly.

| | Kite | Wonder |
|---|---|---|
| Vector editing | Pen tool, point editing and boolean operations | AI-made SVGs, no point editing |
| Components | Components with variants, properties and instance swap | Yes |
| Variables | Variables with modes, like light and dark, set per frame | Yes |
| Auto layout | Rows, columns and grids that grow with their content | Yes |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes |
| Local MCP server | Built into Kite for Mac, for agents on your machine | No |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Yes |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | Unlimited MCP; AI chat tokens |
| AI credits | None: your agent runs on the plan you already pay for | AI tokens, $20 a seat monthly |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Figma | Paste to and from Figma, or import a whole file by its link | Import |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Yes |
| Custom fonts | Upload your own, or use any Google font | Yes |
| Browser extension | Kite Capture copies any web page into Kite as layers | Yes, Capture |
| Desktop app | Kite for Mac and Windows, with a tab for each file | Yes |
| Free plan | Unlimited editors and viewers, and 3 files, free | Yes, limited AI chat tokens |

**Is Kite a good Wonder alternative?** Yes. Kite has no built-in AI to pay for: the agents you already use design in it, with a full vector editor, and take jobs from comments.

Page: https://kite.new/compare/wonder

### Kite vs MagicPath

Kite is a full design tool where the agents you already use draw beside you, with vector editing, variants and modes. In MagicPath, its own agents and outside ones generate React screens that you then edit visually.

Kite is for: Teams that design by hand and with their own agents, in one editor.

Why teams pick Kite over MagicPath:
- A full vector editor, with pen tool and booleans.
- Components with variants, and variables with modes.
- Free includes 200 agent actions a day, and Pro has no cap. MagicPath's free plan gets 50 calls a week.
- @-mention an agent in a comment and it makes the change.

| | Kite | MagicPath |
|---|---|---|
| Vector editing | Pen tool, point editing and boolean operations | Basic |
| Components | Components with variants, properties and instance swap | Basic |
| Variables | Variables with modes, like light and dark, set per frame | Themes |
| Auto layout | Rows, columns and grids that grow with their content | Yes, auto layout |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Yes |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes |
| Several agents at once | Several agents in one file, beside your team | Yes |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | 50 calls a week free |
| AI credits | None: your agent runs on the plan you already pay for | Yes, with packs |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | Per-design revisions, rollback |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | Image, Figma, code |
| Figma | Paste to and from Figma, or import a whole file by its link | Import and export |
| Live cursors | Live cursors and selections for everyone in the file | Yes |
| Comments | Comment threads pinned to the design, with email notifications | Comments on shared designs |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Yes |
| Share links | One link per file, and guests comment with just a name | Yes |
| Custom fonts | Upload your own, or use any Google font | Yes |
| Browser extension | Kite Capture copies any web page into Kite as layers | Yes |
| Desktop app | Kite for Mac and Windows, with a tab for each file | Mac app |
| Free plan | Unlimited editors and viewers, and 3 files, free | 20 credits a day, up to 120 a month |

**Is Kite a good MagicPath alternative?** Yes. Kite is a full design tool where the agents you already use draw beside you, with vector editing, variants and modes.

Page: https://kite.new/compare/magicpath

### Kite vs Subframe

Kite is a design tool for people and the agents they already use, with vector editing and no AI credits. Subframe is a canvas and coding agent for your codebase, with no pen tool, running on AI credits or your Claude or Codex plan.

Kite is for: Teams designing brand, marketing and product work with their own agents.

Why teams pick Kite over Subframe:
- Vector editing with a pen tool. Subframe has none.
- No AI credits at all. Subframe's web app runs on monthly credits.
- Figma both ways. Subframe rebuilds a Figma picture with AI.
- 3 files free. Subframe's free plan has 1 project.

| | Kite | Subframe |
|---|---|---|
| Vector editing | Pen tool, point editing and boolean operations | No |
| Components | Components with variants, properties and instance swap | Yes |
| Variables | Variables with modes, like light and dark, set per frame | Tokens, light and dark modes |
| Auto layout | Rows, columns and grids that grow with their content | Yes, flex stacks and breakpoints |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Yes, about 50 tools |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes |
| Jobs from comments | @-mention an agent in a comment and it makes the change | Through comments |
| Several agents at once | Several agents in one file, beside your team | Async jobs |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | AI credits |
| AI credits | None: your agent runs on the plan you already pay for | Yes, monthly; raise seat tier for more |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | 24 hours to 30+ days, by plan |
| Figma | Paste to and from Figma, or import a whole file by its link | Import with AI |
| Live cursors | Live cursors and selections for everyone in the file | Yes |
| Comments | Comment threads pinned to the design, with email notifications | Yes |
| Share links | One link per file, and guests comment with just a name | Yes |
| Custom fonts | Upload your own, or use any Google font | Yes |
| Desktop app | Kite for Mac and Windows, with a tab for each file | Mac and Windows |
| Free plan | Unlimited editors and viewers, and 3 files, free | Yes, 1 project |

**Is Kite a good Subframe alternative?** Yes. Kite is a design tool for people and the agents they already use, with vector editing and no AI credits.

Page: https://kite.new/compare/subframe

### Kite vs Google Stitch

Kite is a full design tool where the agents you already use draw, edit and take comments. Google Stitch is a free Google Labs tool where Gemini generates UI and code, and outside agents work by prompting Gemini.

Kite is for: Teams that keep editing and reviewing what agents make.

Why teams pick Kite over Google Stitch:
- Agents draw and edit layers themselves. In Stitch, they prompt Gemini to generate screens.
- Variables with modes, like light and dark. Stitch keeps its rules in a DESIGN.md.
- No credits: your agent runs on the plan you already pay for. Stitch has a daily credit limit.
- @-mention an agent in a comment and it makes the change.

| | Kite | Google Stitch |
|---|---|---|
| Variables | Variables with modes, like light and dark, set per frame | DESIGN.md rules |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes |
| Local MCP server | Built into Kite for Mac, for agents on your machine | Yes, official CLI |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Yes, via Gemini prompts |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes, any MCP agent; Gemini generates |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | Daily credits |
| AI credits | None: your agent runs on the plan you already pay for | Daily credits |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | React and HTML |
| Figma | Paste to and from Figma, or import a whole file by its link | Import and export |
| Comments | Comment threads pinned to the design, with email notifications | Yes |
| Share links | One link per file, and guests comment with just a name | Yes |
| Free plan | Unlimited editors and viewers, and 3 files, free | Free, daily credit limit |

**Is Kite a good Google Stitch alternative?** Yes. Kite is a full design tool where the agents you already use draw, edit and take comments.

Page: https://kite.new/compare/stitch

### Kite vs Uizard

Kite is a full design tool where the agents you already use draw beside your team, with components, variants and version history. Uizard makes quick mockups with its own AI, and gives your agents no way to connect.

Kite is for: Designers and teams doing real design work with their own agents.

Why teams pick Kite over Uizard:
- Agents connect to Kite. Uizard has no API to connect them.
- Components with variants and instances. Uizard has templates.
- No AI credits: your agent runs on the plan you already pay for. Uizard counts generations.
- Figma both ways. Uizard imports only.

| | Kite | Uizard |
|---|---|---|
| Components | Components with variants, properties and instance swap | Templates, no linked instances |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | No |
| Local MCP server | Built into Kite for Mac, for agents on your machine | No |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | No way for agents to connect |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Its own AI only |
| Jobs from comments | @-mention an agent in a comment and it makes the change | No |
| Several agents at once | Several agents in one file, beside your team | No |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | Generations |
| AI credits | None: your agent runs on the plan you already pay for | Generations |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Figma | Paste to and from Figma, or import a whole file by its link | Import |
| Live cursors | Live cursors and selections for everyone in the file | Yes |
| Comments | Comment threads pinned to the design, with email notifications | Yes |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Yes |
| Free plan | Unlimited editors and viewers, and 3 files, free | Yes, 3 generations a month |

**Is Kite a good Uizard alternative?** Yes. Kite is a full design tool where the agents you already use draw beside your team, with components, variants and version history.

Page: https://kite.new/compare/uizard

### Kite vs Visily

Kite is a full design tool where the agents you already use draw and edit in your file. Visily's server for agents only reads, so your agent builds from its designs somewhere else.

Kite is for: Teams whose agents draw and edit the design itself.

Why teams pick Kite over Visily:
- Agents draw and edit. Visily's server only reads.
- Agents connect on every plan. Visily's server needs Pro or Business.
- Auto layout on the canvas. Visily's responsive layout is only in its code export.
- @-mention an agent in a comment and it makes the change.

| | Kite | Visily |
|---|---|---|
| Components | Components with variants, properties and instance swap | Yes |
| Variables | Variables with modes, like light and dark, set per frame | Themes |
| Auto layout | Rows, columns and grids that grow with their content | AI responsive, in export |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Pro and Business |
| What agents can do | 59 tools: agents read, draw, edit and check their own work | Read only |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes |
| Agent limits | 200 agent actions a day on Free; unlimited on Pro | Credits |
| AI credits | None: your agent runs on the plan you already pay for | Yes, with top-ups |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | Paid only, 7 to 30 days |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | React, Vue, HTML |
| Figma | Paste to and from Figma, or import a whole file by its link | Import and export |
| Live cursors | Live cursors and selections for everyone in the file | Yes |
| Comments | Comment threads pinned to the design, with email notifications | Yes |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Yes |
| Free plan | Unlimited editors and viewers, and 3 files, free | Yes, 300 credits a month |

**Is Kite a good Visily alternative?** Yes. Kite is a full design tool where the agents you already use draw and edit in your file.

Page: https://kite.new/compare/visily

### Kite vs Relume

Kite is a design canvas where your agents and your team design anything together: screens, brand and pages. Relume builds and hosts marketing sites from its component library, and agents can build and edit them on paid plans.

Kite is for: Teams designing screens, brand and pages with their own agents.

Why teams pick Kite over Relume:
- A canvas for any design, not only marketing sites.
- Auto layout on the canvas. Relume's is in its Figma export.
- A local server in Kite for Mac, so agents on your machine connect directly.
- Figma both ways. Relume exports to Figma.
- @-mention an agent in a comment and it makes the change.

| | Kite | Relume |
|---|---|---|
| Components | Components with variants, properties and instance swap | Yes, a library |
| Variables | Variables with modes, like light and dark, set per frame | Style guide, no modes listed |
| Auto layout | Rows, columns and grids that grow with their content | In Figma export |
| Hosted MCP server | Any agent connects from anywhere, signing in with OAuth | Yes, builds and edits sites (paid) |
| Local MCP server | Built into Kite for Mac, for agents on your machine | No |
| Which agents | Claude, ChatGPT, Cursor, Codex or any MCP client | Yes: Claude, ChatGPT, Cursor, Codex |
| Where files live | In the cloud, open in any browser or in Kite for Mac | Yes |
| Version history | Autosaves every 10 minutes, plus named versions to go back to | Yes |
| Export | PNG, JPG, WebP, AVIF, SVG and PDF, or copy as HTML, React or Tailwind | Figma, Webflow, React, HTML |
| Figma | Paste to and from Figma, or import a whole file by its link | Export to Figma |
| Comments | Comment threads pinned to the design, with email notifications | Yes |
| Workspaces and roles | Workspaces with owner, editor and viewer roles | Yes |
| Free plan | Unlimited editors and viewers, and 3 files, free | Yes |

**Is Kite a good Relume alternative?** Yes. Kite is a design canvas where your agents and your team design anything together: screens, brand and pages.

Page: https://kite.new/compare/relume

## Pages for people comparing design tools

Refreshed 26 October 2026. paper.design is named in full on these pages.

- [The best AI design tools](https://kite.new/alternatives)
- [Figma alternatives](https://kite.new/alternatives/figma) — the longer side-by-side is [Kite vs Figma](https://kite.new/compare/figma)
- [UI design AI](https://kite.new/ai-ui-design) — agents connect over MCP. Docs: [MCP server](https://kite.new/docs/mcp), [working with agents](https://kite.new/docs/agents), [connect a client](https://kite.new/docs/mcp/clients)

## Docs

### Getting started

- [Overview](https://kite.new/docs)
- [Start guide](https://kite.new/docs/start-guide)
- [Keyboard shortcuts](https://kite.new/docs/shortcuts)

### Tutorials

- [Your first design with an agent](https://kite.new/docs/tutorials/first-design-with-an-agent)
- [Put your brand in a design system](https://kite.new/docs/tutorials/brand-design-system)
- [Build a button component](https://kite.new/docs/tutorials/button-component)
- [Move a Figma file to Kite](https://kite.new/docs/tutorials/figma-to-kite)
- [Review a design with your team](https://kite.new/docs/tutorials/review-with-your-team)

### Your files

- [Library and folders](https://kite.new/docs/library)
- [Bring work in](https://kite.new/docs/import)
- [Archive](https://kite.new/docs/archive)

### Design

- [The canvas](https://kite.new/docs/editor/canvas)
- [Drawing tools](https://kite.new/docs/editor/drawing)
- [Layers and pages](https://kite.new/docs/editor/layers)
- [Layout](https://kite.new/docs/editor/layout)
- [Fills, strokes and text](https://kite.new/docs/editor/styling)
- [Components](https://kite.new/docs/components)
- [Design systems](https://kite.new/docs/design-systems)
- [Preview and history](https://kite.new/docs/editor/preview-history)
- [Export and copy](https://kite.new/docs/export)

### Collaborate

- [Sharing](https://kite.new/docs/sharing)
- [Comments](https://kite.new/docs/comments)
- [Workspaces and people](https://kite.new/docs/workspaces)
- [Notifications](https://kite.new/docs/notifications)

### Agents

- [Working with agents](https://kite.new/docs/agents)
- [MCP server](https://kite.new/docs/mcp)
- [Features](https://kite.new/docs/mcp/features)

### Supported clients

- [Choose your client](https://kite.new/docs/mcp/clients)
- [Antigravity](https://kite.new/docs/mcp/clients/antigravity)
- [ChatGPT](https://kite.new/docs/mcp/clients/chatgpt)
- [Claude](https://kite.new/docs/mcp/clients/claude)
- [Claude Code](https://kite.new/docs/mcp/clients/claude-code)
- [Codex](https://kite.new/docs/mcp/clients/codex)
- [Codex app](https://kite.new/docs/mcp/clients/codex-app)
- [Cursor](https://kite.new/docs/mcp/clients/cursor)
- [GitHub Copilot CLI](https://kite.new/docs/mcp/clients/copilot-cli)
- [Grok](https://kite.new/docs/mcp/clients/grok)
- [Manus](https://kite.new/docs/mcp/clients/manus)
- [Muse](https://kite.new/docs/mcp/clients/muse)
- [v0](https://kite.new/docs/mcp/clients/v0)
- [VS Code](https://kite.new/docs/mcp/clients/vscode)
- [Other agents](https://kite.new/docs/mcp/clients/other)

### Apps and integrations

- [Kite for Mac](https://kite.new/docs/mac)
- [Figma](https://kite.new/docs/figma)
- [Kite Capture](https://kite.new/docs/capture)

### Account

- [Account and settings](https://kite.new/docs/account)

### Developers

- [Build an integration](https://kite.new/docs/mcp/build-an-integration)
- [Revoke access](https://kite.new/docs/mcp/revoke)