Ignite UI ships Angular, React, Blazor and Web Components variants of the same components, and a model working from training data blends them into code that reads correctly and fails at runtime. Every tool here takes the framework or platform as an argument and answers from the documentation shipped for that one, offline, at the version installed with the CLI.
The MCP server bundled with the Ignite UI CLI. It answers component documentation, API reference and project setup questions for Ignite UI's Angular, React, Blazor and Web Components libraries, with every lookup scoped to one of them.
- list_components returns the doc catalogue for a framework, filtered by a keyword match against filename, component name, keywords and summary
- get_doc returns one component doc in full by name, resolving bare grid feature names and common aliases
- search_docs runs full-text search inside a single framework's docs, with prefix matching on a trailing asterisk
- search_api finds API entries by keyword, feature name or partial component name, across all four frameworks or one named platform
- get_api_reference returns a component's properties, methods and events, narrowed to a section or to a single member
- get_project_setup_guide returns scaffolding steps — the Ignite UI CLI for Angular, React and Web Components, dotnet new plus NuGet for Blazor — and creates no files
- A usage-guide prompt that tells the agent how to detect the framework from component prefixes and file extensions
Node, and nothing else: it starts as npx -y igniteui-cli mcp and ships its own documentation database and API data, so the default mode needs no key and no network. A --remote flag points documentation lookups at a hosted backend instead; the API reference always reads the bundled data. If you already work in an Ignite UI project, ig ai-config writes the client configuration for you, alongside the companion theming server. MIT.
One command — npm install -g igniteui-cli