About Box Kite
Box Kite is an MCP server for agents writing Box Kite code, with built-in knowledge of the library and its styling engine. It provides tools to look up component contracts and verify whether style values produce CSS.
Key features
- 01Search props, components, nesting keys, and rules
- 02Inspect accepted values and CSS for style props
- 03Review component props, defaults, and accessibility details
- 04Test style props against the real engine
- 05Retrieve library rules and installable blocks
Use cases
- 01Find the right prop or component for a UI task
- 02Check whether a styling value is accepted before rendering
- 03Inspect a component’s keyboard and ARIA behavior
- 04Retrieve a ready-made page or layout block
MCP support
The MCP server exposes six tools for searching Box Kite documentation, inspecting components and props, checking styles, and retrieving rules or blocks. It runs over stdio and includes data built from the library repository at the installed version.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated today
| Parameter | Type | Required | Description |
|---|---|---|---|
| kind | enum | No | Narrow to one corpus. Leave out to search all four.prop | component | nesting | rule |
| limit | integer | No | How many hits (default 12). |
| query | string | Yes | What the UI should do, a CSS property, or a name you half-remember. |
Details
From the project README@box-kite/mcp
The Box Kite MCP server: the retrieval channel for an agent writing Box Kite code. Six tools, at capability level — what may I write, what does this component take, and the one no documentation mirror can answer: does this value actually work.
npx @box-kite/mcp
No key, no network, no state. Everything it answers with was built into it from the library's own repository at the version you install, including the styling engine itself. Node 22 or newer.
Install
Claude Code
claude mcp add box-kite -- npx -y @box-kite/mcp
Cursor, VS Code, Codex, Zed — anything that speaks stdio:
{
"mcpServers": {
"box-kite": { "command": "npx", "args": ["-y", "@box-kite/mcp"] }
}
}
The tools
| tool | what it answers |
|---|---|
search_docs | The prop, component, nesting key or rule for what you are trying to build — ranked across all four, so a goal finds the answer without its name. |
get_props | A style prop's whole record: the CSS it writes, every value it accepts, a measured example, and for a numeric prop its scale measured at 1/2/4/8. |
get_component | One component's contract: props and defaults, sub-parts, the keyboard map and the ARIA it writes. |
check_styles | A prop bag through the real engine: the CSS each prop writes, or why it wrote none. |
get_rules | The rules the library is written by, as an index or in full. |
get_blocks | Whole sections the shadcn CLI installs — a data-grid page, a settings form, a dashboard shell. |
Why check_styles exists
Box Kite accepts a closed set of values per prop, and a value it does not accept produces no rule
and no class name, by design, because a typo must not emit a broken declaration. A development
build warns in the console once the page renders; a production one says nothing at all. The way to
answer "does bgColor="blue-550" work" before anything renders is to hand it to the engine:
check_styles { "props": { "p": 4, "bgColor": "blue-550", "fontSize": 14, "lineHeight": 1.5, "href": "/about" } }
✅ `p` → `.p-4{padding:1rem}`
❌ `bgColor` does not accept "blue-550" — no rule and no class name were written.
✅ `fontSize` → `.fontSize-14{font-size:0.875rem}`
⚠️ `lineHeight` → `.lineHeight-1\.5{line-height:1.5px}` — lineHeight={1.5} is a 1.5px line: lineHeight is direct pixels, …
⚠️ `href` an HTML attribute, not a style prop. It goes in `props={{ "href": … }}`.
The dividers differ per prop — spacing is ÷4, fontSize is ÷16, border width is direct px — which is
why get_props measures a scale rather than describing one.
What else the library ships for agents
AGENTS.mdanddocs/inside the published@box-kite/reactpackage- The skill and rules file:
npx skills add box-kite/box-kite - Every documentation page as markdown at
https://www.box-kite.dev/<route>.md, indexed by llms.txt
MIT © Box Kite
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.