Features
Kite's MCP server gives your AI tool a design file to work in: it reads what is there, draws into it piece by piece while you watch, follows your design system and answers your team's comments.
Tools
Your tool chooses which to use from what you ask it. You never call them yourself.
Files
file_newStart a design file for the banners, posts, ads and logos it makes, so they're kept side by side.
file_listList your files, newest edit first.
file_searchFind a file by what is in it: its pages, its layers' names and their words.
file_infoA file's title, link, who can open it and how many comments it has.
file_shareChange who can open a file: anyone with the link, or only the people listed.
file_archiveArchive a file. Its link stops working until someone unarchives it.
file_settingsHow agents work in one file: whether they build repeated parts as components.
Drawing
file_outlineRead a file's pages and every frame, text, picture and shape on one, with sizes and positions.
editor_focusWhat you have open and selected, so it knows what you mean by “this”.
layer_sourceRead any layer as HTML, to see exactly how it is built.
layer_drawDraw by writing HTML: each piece becomes a frame, or goes inside one.
layer_editChange styles, words, names and positions in place.
layer_copy · layer_nest · layer_removeCopy, move and delete layers.
layer_searchFind layers by name or by their words.
layer_renderSee a frame as you see it, as a picture, to check its work before saying it's done.
picture_add · video_add · font_lookup · font_addPut a picture or a video into a file, check which fonts and weights really exist, and add a font file to the workspace.
guide_readRead Kite's guide to drawing, components, design systems, comments and files before it starts.
finish_workingSay it has finished, so the board stops showing it at work.
Components and libraries
component_make · component_placeMake a button, card or row a component once, then place copies that follow it — one at a time, or many inside layer_draw's HTML (data-component).
component_combine · component_propertiesCombine components into a set of variants, and give it properties: variants, booleans, texts and swaps.
instance_setChoose a copy's variant and set its other properties.
component_detachTurn a copy back into ordinary layers.
library_publish · library_list · library_updateShare a file's components with the rest of the workspace, and keep their copies up to date.
Design systems
system_list · system_readRead your workspace's colours, type, spacing, radii and shadows, what each is for, and the names of its skills, before drawing.
system_newMake a design system from a preset, from variables, or from your website.
system_apply · variable_edit · style_editChoose the system a file uses, and change its variables, modes and styles.
skill_read · skill_editRead the skills that fit what you asked (a brand's look, a guardrail, how posts are made), and keep the ones you tell it to, on a design system or a file.
Comments
comment_list · comment_replyRead what your team said, on which frame, and answer.
request_listThe requests left for it by name in comments: “@Claude make this card denser”.
data-sticky · data-annotatesRead and leave sticky notes on the board, and annotations that explain a frame or a layer.
Kite for Mac
tab_list · tab_openThrough the Mac app only: see which files you have open as tabs, and open one behind the tab you are looking at, so you can watch it work.
Watching it work
Your tool draws one section, card or row at a time, so you see the design come together. While it works, a pill above the toolbar says what it is designing, the frames it is in glow in its colour, and its cursor moves to each thing it places.
Requests in comments
Type @ in a comment to mention a connected tool, as you would a teammate. Ask your tool to check its Kite requests: it finds each one with the frame it was left on, does it, and answers in the thread.
Ready to try it? Set up your client. For what you see in the file while it works, see Working with agents.