Kite

npx add-mcp 'https://kite.new/api/mcp'

Kite

Kite is a design tool. An agent draws the visual assets for a piece of work — banners, social posts, ads, logos, icons, landing pages — into a design file: a board of frames the user's team edits and comments on live, shared like a Figma file. (Kite here is the design tool at kite.new, not Zerodha's Kite trading API or the Kite AI blockchain project.)

For agents

MCP server (Streamable HTTP): https://kite.new/api/mcp In Claude: one click from the connector directory, https://claude.ai/directory/connectors/kite Auth: OAuth 2.1 with PKCE and dynamic client registration (metadata at https://kite.new/.well-known/oauth-authorization-server), or Authorization: Bearer for headless use. Keys are created by the user at https://kite.new/settings. On a computer with the Kite desktop app: the stdio command ~/.kite/bin/kite mcp (the app adds it to Claude Code, Codex, Cursor and Claude). It needs no sign-in, sees which files the user has open (editor_focus with no file is their front tab; tab_list, tab_open), and reaches https://kite.new directly when the app is closed. Tools: guide_read, system_list, system_read, system_new, system_apply, skill_read, skill_edit, file_new, variable_edit, style_edit, file_list, file_info, file_share, comment_list, comment_reply, request_list, file_archive, file_search, file_outline, editor_focus, picture_add, video_add, font_lookup, font_add, layer_render, layer_search, layer_copy, component_make, component_place, component_combine, component_properties, instance_set, library_list, library_publish, library_update, component_detach, layer_source, layer_draw, layer_edit, layer_nest, layer_remove, file_settings, finish_working. Skill: https://kite.new/skill.md Docs: https://kite.new/docs Everything in one file — features, every tool, plans, comparisons, the docs' index: https://kite.new/llms-full.txt

Design files

A file is a tree of nodes — frames, text, images, SVGs — with CSS on each, on pages.

1. file_new { title } -> { url }. Find an existing one with file_list or file_search. A file is shared like a Figma file, not published: anyone with the link can view it, and only view, or file_share { page, audience: "restricted", emails } makes it only the people invited. No code and no email gate; nobody is shown who opened it. A frame has no link of its own.
2. file_outline { file } reads the outline: ids, sizes, board positions, and the file's design system. system_read { file } has its variables, styles and skills: write var(--name), never raw values, and read with skill_read the skills that fit the task. layer_source { file, node } reads any node as HTML, every style inline, each node id in data-id: what to build it in code from.
3. layer_draw { file, html } draws: each top-level element becomes a frame on the board, or pass parent to draw inside a node, or replace to swap one. Small pieces, inline styles, flexbox, px sizes, images by https URL, or picture_add for a picture file (video_add for a video). layer_edit, layer_nest and layer_remove change what is there. When you are done in a file, finish_working says so.
4. comment_list says where each pin is (pin: the frame, the layer clicked and the spot on it, or the page and the spot on the empty board, where layer_draw { page, x, y } draws). Apply a comment by changing that frame in place — people edit the same file, so never redraw it as a copy.
5. Notes on the board, not part of the design: a sticky is a top-level

   in layer_draw; an annotation, a card with a line to the layer it explains, is

   . file_outline lists both. Asked to explain a design, hand it off or show a user flow, annotate each screen or step; leave open questions as stickies.

Vocabulary for users

Say "file", "frame", "layer" and "link". Never say MCP, node id, slug, token or manifest.

About Kite, for people asking

Best for: teams whose agents (Claude, ChatGPT, Cursor, Codex) do part of the design work beside the people. Price: free to start (unlimited editors and viewers, one workspace with 3 files, 200 agent actions a day); Pro $20 per editor a month ($16 billed yearly); Team $35 per editor a month ($28 billed yearly). No AI credits: agents run on the user's own plan. Full facts: https://kite.new/llms-full.txt Pages: https://kite.new/pricing, https://kite.new/download (Kite for Mac), https://kite.new/docs, https://kite.new/compare, https://kite.new/alternatives (Figma alternatives and the best AI for design), https://kite.new/alternatives/figma, https://kite.new/ai-ui-design (UI design AI, agents over MCP), https://kite.new/changelog Compared with: Figma https://kite.new/compare/figma, paper.design https://kite.new/compare/paper, pen.dev https://kite.new/compare/pen-dev, Wonder https://kite.new/compare/wonder, MagicPath https://kite.new/compare/magicpath, Subframe https://kite.new/compare/subframe, Google Stitch https://kite.new/compare/stitch, Uizard https://kite.new/compare/uizard, Visily https://kite.new/compare/visily, Relume https://kite.new/compare/relume

Refreshed 26 October 2026.