Setting Up the Ignite UI CLI MCP Server
April 27, 2026 · View on GitHub
Part of the
igniteui-angular-componentsskill hub.
Contents
The Ignite UI CLI MCP server enables AI assistants to discover Ignite UI components, access component documentation, and support related Ignite UI workflows. It must be configured in your editor before these tools become available.
VS Code
Create or edit .vscode/mcp.json in your project:
{
"servers": {
"igniteui-cli": {
"command": "npx",
"args": ["-y", "igniteui-cli", "mcp"]
}
}
}
This works whether igniteui-cli is installed locally in node_modules or needs to be pulled from the npm registry — npx -y handles both cases.
Cursor
Create or edit .cursor/mcp.json:
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": ["-y", "igniteui-cli", "mcp"]
}
}
}
Claude Desktop
Edit the Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": ["-y", "igniteui-cli", "mcp"]
}
}
}
WebStorm / JetBrains IDEs
- Go to Settings → Tools → AI Assistant → MCP Servers
- Click + Add MCP Server
- Set Command to
npxand Arguments to-y igniteui-cli mcp - Click OK and restart the AI Assistant
Verifying the Setup
After configuring the MCP server, ask your AI assistant:
"List all available Ignite UI components"
If the MCP server is running, the list_components tool will return all available components for the detected framework.