Tooling
PlannedMCP for component library aware AI tooling
The MCP (Model Context Protocol) server is planned as a bridge between the component library documentation and AI tools. Its purpose is to make the component library understandable to code generators, agents, and editor assistants so they can produce Angular code that follows the documented component APIs.
Component documentation should be usable by humans and AI tools
A component library contains more than package exports. It includes design intent, usage rules, composition patterns, tokens, valid variants, accessibility expectations, and examples. MCP gives us a structured way to expose that knowledge to tools that generate or review UI code.
Shared component knowledge
The MCP server can expose component specs, selectors, import paths, examples, recipes, and validation rules from the documentation.
Better AI-generated code
AI tools can ask for the exact FrameUI context they need before generating Angular code, instead of guessing component APIs.
Reusable integration point
The same knowledge source can support the docs AI Composer, local agents, external coding tools, and future automation workflows.
What it brings
A structured knowledge layer for the component library
- Search available components and their documented usage.
- Return selectors, inputs, outputs, imports, and examples for matched components.
- Provide composition recipes for forms, dashboards, menus, modals, and other real UI patterns.
- Validate generated code against known FrameUI and Angular mistakes.
Coming soon
PlannedThe MCP integration is planned. This page is a preview of the intended direction rather than a finished feature.