Model Context Protocol

A local MCP server for UI components

Agentic UI Kit includes agentic-ui, a local MCP server with 9 read-only tools over a catalog of 828 React and Next.js components. Your coding agent calls it to find the component that fits a task, decide whether to reuse, adapt or build, and apply your theme first. It then installs with the agentic-ui CLI or the shadcn CLI, as source files in your repository.

The 9 tools

Every tool is read-only and runs locally over stdio. None of them writes to your project.

Tool	What it returns
understand_project	Reads the project profile, Design DNA and ui-kit.config.yaml. Call it first.
recommend_patterns	Top matches for a natural-language task, with score, suggested composition and availability.
find_reusable_ui	Search by intent and get a reuse / adapt / build-new decision against your reuse threshold.
compare_patterns	Side-by-side comparison of 2–8 components: data shape, density, effort, coupling and quality.
recommend_blueprint	Best multi-screen blueprint for a project type, with the role of each component.
plan_ui_rework	Per-screen modernization plan for conservative, balanced or transformative modes.
explain_pattern	What to preserve, what to replace and when to avoid a component.
resolve_theme	Checks a theme code, preset or spec and returns its summary, AA report and the exact apply command.
list_themes	The 26 curated theme presets with their share codes and apply commands.

How an agent uses it

understand_project: Reads the project profile, its Design DNA and ui-kit.config.yaml, so every answer fits the project.
find_reusable_ui: Searches the catalog by intent and returns a reuse, adapt or build-new decision against the project's reuse threshold.
explain_pattern: Says what to keep, what to replace and when to avoid the component before the agent installs it.
resolve_theme: Checks the theme and returns the exact agentic-ui theme apply command, so the theme is applied before any component.
The agent installs what fits with agentic-ui add <component>, writes only the glue code and runs your build.

A recorded call

find_reusable_ui with the intent “seat usage with plan limits” answered in 26 ms. Decision: adapt Billing Usage Meter (reuse threshold 0.72). Ranked results:

Install

Setup registers the server in your agent's MCP config and copies the 4 agent skills. The full two-step install is on Docs; per-agent guides: Claude Code, Cursor, Codex.

In your project (pass your agent's id instead of detect)

node ~/agentic-ui-kit/bin/agentic-ui.mjs setup --yes --validate --client detect
node ~/agentic-ui-kit/bin/agentic-ui.mjs mcp check

Questions

Is the MCP server hosted?

No. It runs locally over stdio, started by your coding agent from the kit on your machine. It reads the catalog that ships with the kit and the files of your project.

Can the MCP server change my code?

No. All 9 tools are read-only. Installing is done by the agentic-ui CLI or the shadcn CLI, which your agent runs as ordinary commands you can see and approve.

Which agents can use it?

Any MCP client that starts stdio servers. Setup writes the config for 14 clients, including Claude Code, Codex and Cursor; Claude Code and Codex are verified end to end in our recorded runs.

Does it replace the shadcn MCP server?

No, it adds to it. The shadcn MCP server browses and installs registry items. This one answers which catalog component fits a task, whether to reuse, adapt or build, and which theme to apply first.