Enables AI agents to write accurate Box Kite React code by providing tools to inspect components, props, styling rules, and CSS output.
Also known as box-kite/box-kite, mcp, @box-kite/mcp
- Stars
- 12
- Tools
- 6
- Downloads, 30 days
- 4,018
- Latest version
- 2.4.1
- Last commit
- Nov 10, 2026
- License
- MIT
What is Box Kite MCP?
Box Kite enables AI agents to write accurate Box Kite React code by providing tools to inspect components, props, styling rules, and CSS output. It exposes 6 tools, such as search_docs, get_props, get_component.
Summary generated from the project's README
About Box Kite MCP server
Writing accurate Box Kite React code becomes possible for AI agents through this MCP server. It provides a retrieval channel that allows developers to use Claude Code, Cursor, VS Code, or other stdio-compatible clients to inspect components, props, and styling rules. Because the server runs locally via npx and requires no API keys or network connection, it maintains privacy while providing high-fidelity data derived directly from the library repository.
The server includes six specialized tools to assist with development. Developers can use search_docs to find specific nesting keys or rules, get_component to understand a component's contract and ARIA attributes, and get_blocks to access entire sections like dashboard shells or settings forms. A standout feature is the check_styles tool, which runs a prop bag through the actual styling engine to verify if a specific value produces valid CSS or if a typo has resulted in no class name being written.
What you can do with it
- 1Verify style prop valuesCheck if a specific color or spacing value will actually generate a CSS rule before rendering the component.
- 2Inspect component contractsRetrieve the full list of props, default values, and keyboard maps for a specific component.
- 3Discover component scalesDetermine the exact numeric scale and CSS output for a specific style prop.
- 4Generate complex UI layoutsRequest entire pre-built sections like data-grids or dashboard shells to jumpstart development.
Written from the project's README. Every use case is checked against a quote from it.
How to install Box Kite MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Box Kite MCP in Claude Code
$ claude mcp add mcp -- npx -y @box-kite/mcpInstall Box Kite MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@box-kite/mcp"
]
}
}
}Install Box Kite MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@box-kite/mcp"
]
}
}
}Install Box Kite MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@box-kite/mcp"]}'Install Box Kite MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@box-kite/mcp"
]
}
}
}Install Box Kite MCP in Codex
$ codex mcp add mcp -- npx -y @box-kite/mcpInstall Box Kite MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@box-kite/mcp"]
Install Box Kite MCP in Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @box-kite/mcpInstall Box Kite MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@box-kite/mcp"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @box-kite/mcp 2.4.1 in an isolated container with no network and no keys. It answered and listed 6 tools.
Box Kite MCP tools 6
Read from the server with tools/listsearch_docsRead-onlyFind the prop, component, nesting key or rule for what you are trying to build. Ranked across all four, so a goal ("fade in on mount", "sticky header", "right-to-left") finds the answer without knowing its name. Start here.
get_propsRead-onlyThe full record for named style props: the CSS they write, every value they accept, and a measured example — plus, for a numeric prop, the scale measured at 1/2/4/8, because the dividers differ per prop (238 props in all). Nesting keys are answered here too: hover, focus, focusVisible, hasFocus, active, valid, hasValid, invalid, hasInvalid, optional, hasChecked, hasRequired, hasDisabled, visited, target, open, placeholderShown, autofill, inRange, outOfRange, inert, rtl, ltr, indeterminate, checked, required, disabled, selected, before, after, placeholder, selection, marker, firstLine, firstLetter, backdrop, fileButton, sm, md, lg, xl, xxl, pointerCoarse, pointerFine, motionReduce, forcedColors, contrastMore, cq, dataAttr, ariaAttr, has, not, nth, group, peer, theme, startingStyle.
get_componentRead-onlyOne component's whole contract: its props and their defaults, its sub-parts, its keyboard map and the ARIA it writes. Ask before composing a Dialog, Menu, Tabs, Combobox, DataGrid or any other behaviour component — the accessible mechanics are already in it.
check_stylesRead-onlyRun a prop bag through the real styling engine and get back the CSS each prop writes — or why it wrote none. This is the only way to be sure: an unknown prop and an unaccepted value both produce no rule and no class name, with no warning anywhere. Use it on any prop bag you were not certain about, especially numbers and colour tokens.
get_rulesRead-onlyThe 56 rules this library is written by — where the element comes from, where HTML attributes go, how a layer is anchored, how a theme scopes. With no arguments it lists all 56 headings; pass numbers for the ones you need in full.
get_blocksRead-onlyWhole sections rather than atoms — a data-grid page, a settings form, a dashboard shell — installed by the shadcn CLI, which also installs the package. Reach for one before composing a large surface by hand.
| search_docs | Find the prop, component, nesting key or rule for what you are trying to build. Ranked across all four, so a goal ("fade in on mount", "sticky header", "right-to-left") finds the answer without knowing its name. Start here. | Read-only |
| get_props | The full record for named style props: the CSS they write, every value they accept, and a measured example — plus, for a numeric prop, the scale measured at 1/2/4/8, because the dividers differ per prop (238 props in all). Nesting keys are answered here too: hover, focus, focusVisible, hasFocus, active, valid, hasValid, invalid, hasInvalid, optional, hasChecked, hasRequired, hasDisabled, visited, target, open, placeholderShown, autofill, inRange, outOfRange, inert, rtl, ltr, indeterminate, checked, required, disabled, selected, before, after, placeholder, selection, marker, firstLine, firstLetter, backdrop, fileButton, sm, md, lg, xl, xxl, pointerCoarse, pointerFine, motionReduce, forcedColors, contrastMore, cq, dataAttr, ariaAttr, has, not, nth, group, peer, theme, startingStyle. | Read-only |
| get_component | One component's whole contract: its props and their defaults, its sub-parts, its keyboard map and the ARIA it writes. Ask before composing a Dialog, Menu, Tabs, Combobox, DataGrid or any other behaviour component — the accessible mechanics are already in it. | Read-only |
| check_styles | Run a prop bag through the real styling engine and get back the CSS each prop writes — or why it wrote none. This is the only way to be sure: an unknown prop and an unaccepted value both produce no rule and no class name, with no warning anywhere. Use it on any prop bag you were not certain about, especially numbers and colour tokens. | Read-only |
| get_rules | The 56 rules this library is written by — where the element comes from, where HTML attributes go, how a layer is anchored, how a theme scopes. With no arguments it lists all 56 headings; pass numbers for the ones you need in full. | Read-only |
| get_blocks | Whole sections rather than atoms — a data-grid page, a settings form, a dashboard shell — installed by the shadcn CLI, which also installs the package. Reach for one before composing a large surface by hand. | Read-only |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@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
Box Kite MCP questions
How do I add Box Kite MCP to Claude Code?
Run claude mcp add mcp -- npx -y @box-kite/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Box Kite MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Box Kite MCP provide?
It exposes 6 tools, including search_docs, get_props, get_component, check_styles, get_rules.
Does the server require an API key or network connection?
No, the server requires no key, no network, and maintains no state.
How can I verify if a specific style prop value will work before rendering?
You can use the check_styles tool to pass a prop bag through the real engine to see exactly what CSS is written or why a value failed.
What version of Node.js is required?
You need Node 22 or newer to run the server.
What happens if I provide a value that a prop does not accept?
The engine will produce no rule and no class name to prevent broken declarations.