Ignite UI CLI
Ignite UI CLI scaffolds Angular, React and Web Components projects, and ig ai-config sets up MCP servers and skills.
- 138 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The `ig ai-config` command creates and changes configuration and instruction files in the project.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ignite-ui-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The `ig ai-config` command creates and changes configuration and instruction files in the project.
This is third-party code. Review the repository files before installing.
What it does
Ignite UI CLI from the Infragistics repository creates a project, adds views with components such as a grid or chart, and builds it. Angular, React, Web Components, Blazor and jQuery are supported, with theme selection and a step-by-step mode. For agents the CLI has two layers. The `ig ai-config` command writes MCP servers into `.mcp.json`, `.vscode/mcp.json` or `.cursor/mcp.json`, copies skills and generates instructions such as `CLAUDE.md` and `AGENTS.md`. The `ig mcp` command starts a bundled server with Ignite UI documentation search and an API reference.
Who it is for. Front-end teams on Ignite UI who want an agent to know the library components and API instead of guessing them.
Good fit when
- A new Angular or React project starts with an Ignite UI grid and dashboard.
- An agent in Cursor or Claude Code mixes up Ignite UI component properties and needs an exact reference.
- A repository needs MCP configuration and instruction files for several assistants at once.
- You want a grid-editing example found in the documentation by keyword.
Not a fit when
- The project does not use Ignite UI: the server answers only about this library.
- You need a different UI library or design system.
- Code generation cannot run in a closed environment without npm access.
Example request
Find an Ignite UI for Angular grid-editing example in the documentation and show the relevant component properties.Limitations
The server knows only Ignite UI documentation and the API for Angular, React, Blazor and Web Components. Node.js must be installed, and by default documentation comes from a local SQLite database; the `--remote` option switches to a remote address. The `ig ai-config` command creates and updates configuration files, so review the changes in the repository before committing. For Blazor a project is created through `dotnet new` and NuGet rather than `ig`.
How to disable. Remove the `igniteui-cli` and `igniteui-theming` entries from the MCP configuration file, plus the instruction files and copied skills created by `ig ai-config`.
FAQ
Which tools does the MCP server provide?
Six: `list_components`, `get_doc`, `search_docs`, `search_api`, `get_api_reference` and `get_project_setup_guide`. They search documentation, return the API reference and explain how to create a project.
How do I connect the server manually?
Add `igniteui-cli` to the client configuration with the command `npx -y igniteui-cli mcp`. For theming, `igniteui-theming` runs alongside with `npx -y igniteui-theming igniteui-theming-mcp`.
What does ig ai-config do?
It asks which agents get skills and instructions and which assistants get MCP entries. You can pass `--agents claude copilot generic --assistants vscode cursor` directly.
How do I debug the server?
Run `npx @modelcontextprotocol/inspector ig mcp`. The `ig mcp --debug` flag writes a log to `mcp-server.log`.
Which frameworks does the CLI support?
Angular, React, Web Components, Blazor and jQuery. For Blazor the `get_project_setup_guide` tool suggests `dotnet new` and NuGet instead of `ig`.
Discussion
No questions or reviews yet.
Related
CLI toolsigniteui-theming: Ignite UI themes for an AI agent
igniteui-theming
Infragistics MCP server builds palettes, typography and shadows for Ignite UI components on Angular, React, Web Components, Blazor
Angular’s official CLI creates application workspaces, starts development servers and supports ongoing project maintenance.
A skill and MCP server for the spartan/ui Angular library: the agent installs components and blocks from current docs.
The CodeRocket MCP server gives an agent a saved library's design rules, components and blocks over a read-only connection.
The Arc UI MCP server: an agent searches animated React components, reads docs and props and gets the shadcn install command.
Chakra UI MCP server: a reference for components, props and theme tokens, plus code review for moving from version 2 to 3
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Ignite UI CLI (this card) | no | not required | 138 | |
| Angular CLI | no | 27,016 | the general Angular CLI; Ignite UI CLI scaffolds projects with Infragistics components and gives agents MCP over their API | |
| Angular Skills | no | 101,486 | a set of Angular skills; this one holds the reference and templates of a single component library |
README in short
The monorepo combines several packages into `igniteui-cli`: the core, templates, Angular schematics and the MCP server.