Ignite UI CLI 15 – MCP Server, ai-config & Blazor Scaffolding

Ignite UI CLI 15 – MCP Server, ai-config & Blazor Scaffolding

Ignite UI CLI 15 (releases 15.0.0 through 15.5.0) turns the CLI into the setup layer of the Ignite UI AI-assisted development toolchain. Highlights: the Ignite UI CLI MCP server with documentation and API lookup for AI assistants across Angular, React, Web Components, and Blazor; the ai-config command for one-command Agent Skills and MCP configuration; Blazor project scaffolding via dotnet new igb-blazor; and modernized Angular templates on signals and Angular 22. CLI 15.0.0 removes the legacy igx-ts-legacy, ig-ts, and igr-es6 project types.

7 min read

Ignite UI CLI 15 is now available, covering feature releases 15.0.0 (April 2026) through 15.5.0 (July 2026). This release line turns the CLI into the setup layer of the Ignite UI AI-assisted development toolchain, alongside the broader Infragistics Ultimate 26.1 release.

What’s new in Ignite UI CLI 15

  • Ignite UI CLI MCP server – documentation search, API reference lookup, and project setup tools for AI coding assistants across Angular, React, Web Components, and Blazor
  • ai-config command – one command copies Agent Skills and writes MCP server configuration into your project
  • Blazor project scaffolding – scaffold Blazor Web Apps with dotnet new igb-blazor, with bootstrap, material, fluent, and indigo themes (15.4.0)
  • Modernized templates – Angular templates rewritten on signals, inject(), and built-in control flow; updated to Angular 22; new side-nav-mini template

⚠️ Breaking changes in 15.0.0: legacy project types removed (see below)
📦 npm install -g igniteui-cli@15.5.0
📄 Full changelog

Ignite UI CLI MCP Server

CLI 15.0.0 introduces the Ignite UI CLI MCP server, a Model Context Protocol server that gives AI coding assistants grounded access to Ignite UI documentation and API reference. It exposes six tools – list_components, get_doc, search_docs, get_api_reference, search_api, and get_project_setup_guide – and runs in two modes: Remote (live docs backend) or Local (bundled SQLite database with full-text search).

The server exists to close a measured gap. In the paired benchmark study, assistants without Ignite UI tooling ignored the library entirely in three of seven scenarios (0/5 library compliance) while the grounded runs scored 5/5 – the full data is in the empirical study of MCP and Agent Skills benefits, and the mechanism behind the failure mode is explained in why Ignite UI AI tooling produces better results.

The server matured across the release line: official Blazor documentation and API support arrived in 15.2.0, get_api_reference gained member-level lookup via a member parameter in 15.2.2, and API links inside MCP-served docs now resolve through the tool instead of external HTML pages. The server has been listed on registry.modelcontextprotocol.io since 15.1.0.

# Launch the Ignite UI CLI MCP server
npx -y igniteui-cli mcp

# Or, with the CLI installed globally
ig mcp

One-Command AI Configuration

The ai-config command (15.1.0) configures AI assistance for an existing project in one command: it copies Agent Skills from the installed Ignite UI package and writes CLI MCP and Theming MCP server entries to .vscode/mcp.json. The servers are configured, not started – you start each one in your AI client, with Claude Code as the exception (it starts servers automatically on first tool invocation).

15.2.0 extends ai-config to Blazor projects and adds a --framework / -f option; when omitted, the framework is auto-detected from package.json, .csproj, or project configuration. During project creation, the --agents and --assistants options apply the same configuration, and the Angular schematics run a dedicated ai-config step during ng new. Supported clients include VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.

# Configure Agent Skills + MCP servers in an existing project
npx igniteui-cli ai-config

# Specify the framework explicitly (Blazor supported since 15.2.0)
npx igniteui-cli ai-config --framework blazor

Explore the AI-assisted development toolchain ->

Blazor Project Scaffolding in 15.4.0

CLI 15.4.0 adds Blazor project creation to the new command, with hosting and variant options, and introduces the EmptyIgbProject template for scaffolding Blazor Web Apps directly from the .NET CLI. The template supports the bootstrap, material, fluent, and indigo themes.

# Scaffold a Blazor Web App with the EmptyIgbProject template
ig new blazor-app --framework=blazor

For what shipped in the Blazor components themselves, see the Ignite UI for Blazor 26.1 release blog.

Angular 22 support in 15.4.0

15.4.0 release updates igniteui-angular and @angular/core to ~22.0.0 across CLI templates and schematics, so new Angular scaffolds land on Angular 22. For more details, see the Ignite UI for Angular 22.0 release blog.

Modernized Project Templates

CLI 15.0.0 rewrites all 34 Angular template files to current Angular patterns: signal-based viewChild() and output(), inject() instead of constructor injection, built-in @if / @for / @switch control flow, and standalone components with provider functions. Karma/Jasmine is replaced with Vitest and Playwright for testing.

Every scaffolded project is AI-ready out of the box: AGENTS.md and CLAUDE.md guideline files, a pre-wired .vscode/mcp.json, and Agent Skills copied from the installed package. React gains 30 component templates to match Web Components coverage (15.0.0), and 15.3.0 adds a side-nav-mini template – a compact navigation that collapses to icon-only mode – for Angular, React, and Web Components.

More in These Releases

  • Grid component type selection for React (tree, hierarchical, pivot) during project creation (15.4.0)
  • Improved ai-config output: reports how the framework was detected and which Agent Skills source (package and version) is used (15.2.2)
  • Template package references updated to igniteui-angular ~21.2.5, igniteui-react ~19.7.0, igniteui-webcomponents ~7.2.0 (15.2.2)
  • Cleaner CLI error handling: command validation errors and unknown commands print help instead of stack traces
  • ng add igniteui-angular fix: default fonts, Material icons, and provideAnimations correctly added (15.4.1)

What’s New in 15.5.0

CLI 15.5.0 (July 2026) delivers targeted improvements to the MCP server and updates scaffolded package versions for Web Components and React.

MCP server improvements

  • Improved search_docs result ranking and get_doc name resolution for more accurate and relevant results when working with AI coding assistants
  • Enhanced MCP server tool descriptions for better clarity and guidance in AI client interfaces

Updated package versions

Scaffolded Web Components, React, and React Grids projects now reference the latest package versions, so new projects start with up-to-date dependencies out of the box.

# Install or update to 15.5.0
npm install -g igniteui-cli@15.5.0

View the 15.5.0 release notes ->

⚠️ Breaking Changes & Migration

Legacy project types removed (15.0.0)
Affected: igx-ts-legacy (Angular NgModules), ig-ts (Angular wrappers), igr-es6 (React ES6 wrappers)
What changed: these project types are no longer available for scaffolding -> use igx-ts for Angular and igr-ts for React
Migration: no action for existing projects – the removal affects new scaffolding only
View the 15.0.0 release notes ->

Default framework changed (15.0.0)
Affected: the step-by-step interactive guide
What changed: the default framework is now Angular instead of jQuery
Migration: select your framework explicitly if you rely on the previous default

Install Ignite UI CLI 15

# Install globally
npm install -g igniteui-cli@15.5.0

# Or run on demand without installing
npx igniteui-cli@15.5.0 --help
igniteui-cli on npm

Ignite UI CLI 15 FAQ

Does upgrading to Ignite UI CLI 15 break my existing projects?
No. The 15.0.0 removal of igx-ts-legacy, ig-ts, and igr-es6 affects new scaffolding only. Existing projects generated with those types continue to build; you cannot create new projects from them.

Which frameworks does the Ignite UI CLI MCP server cover?
Angular, React, and Web Components since 15.0.0, and Blazor since 15.2.0. Documentation search, API reference lookup, and project setup guides are available for all four.

Do I need to install the CLI globally to use the MCP server?
No. Run npx -y igniteui-cli mcp to launch the server without a global install. With a global install, ig mcp does the same.

Does ai-config start the MCP servers for me?
No. It writes CLI MCP and Theming MCP server entries to .vscode/mcp.json and copies Agent Skills, but you start each server in your AI client. Claude Code is the exception – it starts configured servers automatically on the first tool invocation.

Which AI clients are supported?
VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.

Which Angular version do new scaffolds target?
Angular 22. CLI 15.4.0 updated igniteui-angular and @angular/core to ~22.0.0 across CLI templates and schematics.

Get Started with Ignite UI CLI 15

Scaffold a project, run ai-config, and start the MCP server in your AI client to work against grounded Ignite UI documentation.

Get Started ->
Full Release Notes
Join the Discussion

AI Engineering Ignite UI CLI MCP
Request a Demo