Box Kite

io.github.box-kitePublished by GitHub account box-kitev2.4.0Updated Nov 7, 2026

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

The publisher's own server: Kite

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an assistant Box Kite's React styling knowledge and a real engine check of whether a style value writes CSS.

What you can do
  • Search docs for the prop, component, nesting key or rule matching a build goal
  • Look up a style prop's record: CSS written, accepted values, measured scale
  • Look up a component's contract: props, defaults, sub-parts, keyboard map, ARIA
  • Run a prop bag through the real engine to see the CSS each prop writes or why none was written
  • Read the library's rules as an index or in full
  • Fetch whole shadcn-installed sections such as data-grid pages, settings forms and dashboard shells
When to use it
Useful when an assistant writes or reviews Box Kite React code and needs to confirm which props and values are valid before rendering, especially since invalid values silently produce no CSS in production builds.
Requirements
Runs locally over stdio via npx from the npm package @box-kite/mcp; Node 22 or newer. No API key, network access or state is needed, and all answers come from the library version installed.
Before you install
No credentials or network use are involved. Answers reflect only the installed library version, so results can differ from other Box Kite versions; the server is read-only and does not modify code.

Installation

In SourceWeft

  1. Open Box Kite in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

bash
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

bash
claude mcp add box-kite -- npx -y @box-kite/mcp

Cursor, VS Code, Codex, Zed — anything that speaks stdio:

json
{  "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

Source: mcp/README.md at commit d901f9d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

11
  1. v2.4.0LatestNov 7, 2026
  2. v2.3.0Nov 4, 2026
  3. v2.2.18Nov 4, 2026
  4. v2.2.17Nov 3, 2026
  5. v2.2.16Nov 3, 2026
  6. v2.2.13Oct 30, 2026
  7. v2.2.12Oct 29, 2026
  8. v2.2.7Oct 19, 2026
  9. v2.2.6Oct 19, 2026
  10. v2.2.5Oct 17, 2026
  11. v2.2.4Oct 13, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Kite integrations