io.github.box-kite/mcp·Dev tools

Box Kite

Box Kite's React styling engine as tools: props, components, and whether a value writes CSS.

Stars
7
Version
2.2.3
License
MIT
Review
Passed
Language
TypeScript
Last commit
2h ago
Forks
0
Open issues
0
Registry update
Oct 13, 2026
accessibilityaicss-in-jsdark-modedatagriddesign-systemgenerative-uimcpreactreact-componentsserver-componentsstyling

Connect

npm
Terminal
$claude mcp add mcp \  -- npx -y @box-kite/[email protected]

Environment variables

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 43m ago.

metadata
scanned
packages
1 checked

No findings.

Tools

This server runs on your machine, so its tool list is not fetched before install — the README below describes what it offers.

@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

toolwhat it answers
search_docsThe 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_propsA 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_componentOne component's contract: props and defaults, sub-parts, the keyboard map and the ARIA it writes.
check_stylesA prop bag through the real engine: the CSS each prop writes, or why it wrote none.
get_rulesThe rules the library is written by, as an index or in full.
get_blocksWhole 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.md and docs/ inside the published @box-kite/react package
  • 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

From the server's repository — third-party content, read it before running anything it suggests.

More in Dev tools

Listing from the official MCP Registry · repository facts from GitHub, just now.