@jtl-software/library-mcp
v0.1.0
Published
MCP server exposing JTL platform component metadata to AI agents
Downloads
90
Keywords
Readme
@jtl-software/library-mcp
MCP server that exposes JTL platform component metadata to AI agents so they can browse, inspect, search and get recommendations for the component library without scanning source files.
This package ships a snapshot (registry.json) generated from
both platform libraries: @jtl-software/platform-ui-react (read from its
published dist typings) and @jtl/platform-internal-react (read from in-repo
source). The snapshot is regenerated and re-published on every release, so it
tracks the library versions it was built against (sourceVersion in every
response).
v1 is stdio-only. The snapshot currently covers 95 components (71 base UI + 24 internal); scope grows per release.
Install into an AI agent
npx @jtl-software/library-mcp install <agent> [--local]--local writes to the project directory instead of global config. Supported
agents: claude-code, claude, cursor, windsurf, gemini, codex,
cline, copilot, kilo, pi, hermes, antigravity.
Example (Claude Code, project-local .mcp.json):
npx @jtl-software/library-mcp install claude-code --localRun the server directly
npx @jtl-software/library-mcp stdioMCP tools
| Tool | Purpose |
| ---------------------------------- | ----------------------------------------------------------------- |
| get_minimal_context | Compact overview; call first. |
| list_components | List components, optionally by category. |
| get_component / get_components | Full metadata for one/many components. |
| search_components | Keyword search with relevance ranking. |
| suggest_component | Recommend components for a described UI task. |
| get_composition | Sub-exports and composition patterns (compound components). |
| map_native_html | Map raw HTML tags to the JTL component that replaces them. |
| init | Install commands + Tailwind v4 CSS setup for the runtime library. |
| get_tokens | Design tokens (empty in v1). |
Resources: component://{name}, component://{name}/example,
composition://{name}.
Develop
pnpm install
pnpm generate-registry # regenerate registry.json from library typings/source
pnpm build # tsc -> dist/
pnpm test # vitest
pnpm dev:stdio # run the stdio server from sourceregistry.json is committed (the bundled snapshot) and refreshed by
generate-registry.
