Two frameworks, one shape
Angular and React libraries are analyzed into the same metadata schema, so every tool, formatter and validator works across both.
cl-mcp
Accurate, build-time metadata for Angular & React component libraries — served to LLMs over MCP.
4
packages
6
MCP tools
2
frameworks
1
metadata shape
Why cl-mcp?
Section titled “Why cl-mcp?”LLMs guess component APIs. cl-mcp gives them the real thing: inputs/props,
outputs/callbacks, selectors/JSX names, content projection, config tokens and
Storybook examples — extracted straight from your library’s source at build
time, then served over the Model Context Protocol.
Build-time truth
Metadata comes from TypeScript AST analysis, not runtime reflection or guesswork — deprecations, inheritance and literal-union types included.
MCP or CLI
Use the stdio MCP server from any client, or the cl-mcp CLI for agents
without an MCP client, for CI, and for humans.
Multi-library workspaces
Point it at a cl-mcp.yaml and it analyzes every library, emits per-library
metadata plus a cross-library import graph manifest.
Next steps
Section titled “Next steps”IntroductionWhat the project is and how the pieces fit together.
Quick StartGenerate metadata and run the server in a few commands.
MCP ToolsThe six tools exposed to LLMs.
API ReferenceAuto-generated from @cl-mcp/core and @cl-mcp/analyzer.