list_componentsLABSCO SUMMARY
Four libraries whose class names differ by a prefix, kept apart.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — npm install -g igniteui-cli
USE CASES
01
Adding a grid feature you have not used before
Find the component docs for your framework, then read the one that covers the feature in full rather than working from a snippet.
02
Checking a property actually exists
Search the API entries for the name you are about to write, then read that component's properties, methods and events to confirm the spelling and the type.
03
Porting a component between Ignite UI frameworks
Look the same component up under both platforms and compare the API surfaces, instead of guessing at the prefix and the member names.
04
Starting a project on the right scaffolding
Ask for the setup guide for your framework — CLI steps for Angular, React and Web Components, dotnet and NuGet for Blazor. It tells you what to run and writes nothing itself.
05
Finding the doc when you only know the symptom
Full-text search the framework's docs with the words from the error or the behaviour, then open the page that matches.
6 tools
Listed in project docs. Your client may show a different list.
get_docsearch_docssearch_apiget_api_referenceget_project_setup_guideBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g igniteui-cliMCP Clients
VS Code
Inside your Ignite UI project, run ig ai-config (the ig command comes with npm install -g igniteui-cli).
When it asks which coding assistants to configure MCP servers for, choose VS Code: it writes .vscode/mcp.json with the Ignite UI MCP and igniteui-theming servers and keeps any servers already there.
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": [
"-y",
"igniteui-cli",
"mcp"
]
},
"igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming",
"igniteui-theming-mcp"
]
}
}
}
