{"id":4065,"date":"2026-08-05T15:01:04","date_gmt":"2026-08-05T15:01:04","guid":{"rendered":"https:\/\/www.infragistics.com\/blogs\/?p=4065"},"modified":"2026-08-07T11:34:12","modified_gmt":"2026-08-07T11:34:12","slug":"ignite-ui-cli-15","status":"publish","type":"post","link":"https:\/\/www.infragistics.com\/blogs\/ignite-ui-cli-15","title":{"rendered":"Ignite UI CLI 15 &#8211; MCP Server, ai-config &#038; Blazor Scaffolding"},"content":{"rendered":"<p><!--\nTITLE: Ignite UI CLI 15 - MCP Server, ai-config & Blazor Scaffolding\nMETA DESCRIPTION: Ignite UI CLI 15 ships the Ignite UI CLI MCP server, the ai-config command, and Blazor project scaffolding. See what's new in 15.0-15.5 and how to upgrade.\nSLUG: ignite-ui-cli-15\nEXCERPT: 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.\nNOTE: Hero image block intentionally omitted per PO decision. A WordPress Featured Image MUST still be set - it supplies the Open Graph \/ LinkedIn preview image.\nNOTE: FAQ section integrated (anchor #ignite-ui-cli-15-faq) per release-blog-ai-writing-rules.md \u00a76. Every answer derives from facts already in the dev\/marketing-approved body - no new claims. Set Rank Math -> Schema -> FAQ, or paste the FAQPage JSON-LD at the end of this file. Do not do both.\n--><\/p>\n\n\n<p class=\"wp-block-paragraph\">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 <a href=\"https:\/\/www.infragistics.com\/blogs\/whats-new-in-infragistics-ultimate-26-1\">Infragistics Ultimate 26.1 release<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What&#8217;s new in Ignite UI CLI 15<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Ignite UI CLI MCP server<\/strong> &#8211; documentation search, API reference lookup, and project setup tools for AI coding assistants across Angular, React, Web Components, and Blazor<\/li>\n\n\n\n<li><strong>ai-config command<\/strong> &#8211; one command copies Agent Skills and writes MCP server configuration into your project<\/li>\n\n\n\n<li><strong>Blazor project scaffolding<\/strong> &#8211; scaffold Blazor Web Apps with <code>dotnet new igb-blazor<\/code>, with bootstrap, material, fluent, and indigo themes (15.4.0)<\/li>\n\n\n\n<li><strong>Modernized templates<\/strong> &#8211; Angular templates rewritten on signals, <code>inject()<\/code>, and built-in control flow; updated to Angular 22; new side-nav-mini template<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u26a0\ufe0f Breaking changes in 15.0.0: legacy project types removed (see below)<br>\n\ud83d\udce6 <code>npm install -g igniteui-cli@15.5.0<\/code><br>\n\ud83d\udcc4 <a href=\"https:\/\/github.com\/IgniteUI\/igniteui-cli\/releases\" rel=\"noopener\">Full changelog<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"ignite-ui-cli-mcp-server\" class=\"wp-block-heading\">Ignite UI CLI MCP Server<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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 &#8211; <code>list_components<\/code>, <code>get_doc<\/code>, <code>search_docs<\/code>, <code>get_api_reference<\/code>, <code>search_api<\/code>, and <code>get_project_setup_guide<\/code> &#8211; and runs in two modes: Remote (live docs backend) or Local (bundled SQLite database with full-text search).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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 &#8211; the full data is in the <a href=\"https:\/\/www.infragistics.com\/blogs\/empirical-study-of-mcp-and-agent-skills-benefits\">empirical study of MCP and Agent Skills benefits<\/a>, and the mechanism behind the failure mode is explained in <a href=\"https:\/\/www.infragistics.com\/blogs\/why-ignite-ui-ai-tooling-produces-better-results\">why Ignite UI AI tooling produces better results<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The server matured across the release line: official Blazor documentation and API support arrived in 15.2.0, <code>get_api_reference<\/code> gained member-level lookup via a <code>member<\/code> 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.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Launch the Ignite UI CLI MCP server\nnpx -y igniteui-cli mcp\n\n# Or, with the CLI installed globally\nig mcp\n<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"one-command-ai-configuration\" class=\"wp-block-heading\">One-Command AI Configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>ai-config<\/code> 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 <code>.vscode\/mcp.json<\/code>. The servers are configured, not started &#8211; you start each one in your AI client, with Claude Code as the exception (it starts servers automatically on first tool invocation).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">15.2.0 extends <code>ai-config<\/code> to Blazor projects and adds a <code>--framework<\/code> \/ <code>-f<\/code> option; when omitted, the framework is auto-detected from <code>package.json<\/code>, <code>.csproj<\/code>, or project configuration. During project creation, the <code>--agents<\/code> and <code>--assistants<\/code> options apply the same configuration, and the Angular schematics run a dedicated <code>ai-config<\/code> step during <code>ng new<\/code>. Supported clients include VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Configure Agent Skills + MCP servers in an existing project\nnpx igniteui-cli ai-config\n\n# Specify the framework explicitly (Blazor supported since 15.2.0)\nnpx igniteui-cli ai-config --framework blazor\n<\/pre>\n\n\n\n<figure class=\"wp-block-video\"><video controls src=\"https:\/\/static.infragistics.com\/marketing\/Videos\/ig\/cli-ai-config.mp4\"><\/video><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.infragistics.com\/ai-assisted-app-development\">Explore the AI-assisted development toolchain -&gt;<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"blazor-project-scaffolding-and-angular-22\" class=\"wp-block-heading\">Blazor Project Scaffolding in 15.4.0<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CLI 15.4.0 adds Blazor project creation to the <code>new<\/code> 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.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Scaffold a Blazor Web App with the EmptyIgbProject template\nig new blazor-app --framework=blazor\n<\/pre>\n\n\n\n<figure class=\"wp-block-video\"><video controls src=\"https:\/\/static.infragistics.com\/marketing\/Videos\/ig\/blazor-scaffolding.mp4\"><\/video><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For what shipped in the Blazor components themselves, see the <a href=\"https:\/\/www.infragistics.com\/blogs\/ignite-ui-for-blazor-26-1\">Ignite UI for Blazor 26.1 release blog<\/a>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"angular-22-support-in-15-4-0\">Angular 22 support in 15.4.0<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">15.4.0 release updates <code>igniteui-angular<\/code> and <code>@angular\/core<\/code> to ~22.0.0 across CLI templates and schematics, so new Angular scaffolds land on Angular 22. For more details, see the <a href=\"https:\/\/www.infragistics.com\/blogs\/ignite-ui-for-angular-22\">Ignite UI for Angular 22.0 release blog.<\/a><\/p>\n\n\n\n<h2 id=\"modernized-project-templates\" class=\"wp-block-heading\">Modernized Project Templates<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CLI 15.0.0 rewrites all 34 Angular template files to current Angular patterns: signal-based <code>viewChild()<\/code> and <code>output()<\/code>, <code>inject()<\/code> instead of constructor injection, built-in <code>@if<\/code> \/ <code>@for<\/code> \/ <code>@switch<\/code> control flow, and standalone components with provider functions. Karma\/Jasmine is replaced with Vitest and Playwright for testing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every scaffolded project is AI-ready out of the box: <code>AGENTS.md<\/code> and <code>CLAUDE.md<\/code> guideline files, a pre-wired <code>.vscode\/mcp.json<\/code>, 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 &#8211; a compact navigation that collapses to icon-only mode &#8211; for Angular, React, and Web Components.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"more-in-these-releases\" class=\"wp-block-heading\">More in These Releases<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Grid component type selection for React (tree, hierarchical, pivot) during project creation (15.4.0)<\/li>\n\n\n\n<li>Improved <code>ai-config<\/code> output: reports how the framework was detected and which Agent Skills source (package and version) is used (15.2.2)<\/li>\n\n\n\n<li>Template package references updated to <code>igniteui-angular<\/code> ~21.2.5, <code>igniteui-react<\/code> ~19.7.0, <code>igniteui-webcomponents<\/code> ~7.2.0 (15.2.2)<\/li>\n\n\n\n<li>Cleaner CLI error handling: command validation errors and unknown commands print help instead of stack traces<\/li>\n\n\n\n<li><code>ng add igniteui-angular<\/code> fix: default fonts, Material icons, and <code>provideAnimations<\/code> correctly added (15.4.1)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"whats-new-in-15-5-0\" class=\"wp-block-heading\">What&#8217;s New in 15.5.0<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CLI 15.5.0 (July 2026) delivers targeted improvements to the MCP server and updates scaffolded package versions for Web Components and React.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>MCP server improvements<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Improved <code>search_docs<\/code> result ranking and <code>get_doc<\/code> name resolution for more accurate and relevant results when working with AI coding assistants<\/li>\n\n\n\n<li>Enhanced MCP server tool descriptions for better clarity and guidance in AI client interfaces<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Updated package versions<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Install or update to 15.5.0\nnpm install -g igniteui-cli@15.5.0\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/github.com\/IgniteUI\/igniteui-cli\/releases\/tag\/15.5.0\" rel=\"noopener\">View the 15.5.0 release notes -&gt;<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"breaking-changes-migration\" class=\"wp-block-heading\">\u26a0\ufe0f Breaking Changes &amp; Migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Legacy project types removed (15.0.0)<\/strong><br>\nAffected: <code>igx-ts-legacy<\/code> (Angular NgModules), <code>ig-ts<\/code> (Angular wrappers), <code>igr-es6<\/code> (React ES6 wrappers)<br>\nWhat changed: these project types are no longer available for scaffolding -&gt; use <code>igx-ts<\/code> for Angular and <code>igr-ts<\/code> for React<br>\nMigration: no action for existing projects &#8211; the removal affects new scaffolding only<br>\n<a href=\"https:\/\/github.com\/IgniteUI\/igniteui-cli\/releases\/tag\/15.0.0\" rel=\"noopener\">View the 15.0.0 release notes -&gt;<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Default framework changed (15.0.0)<\/strong><br>\nAffected: the step-by-step interactive guide<br>\nWhat changed: the default framework is now Angular instead of jQuery<br>\nMigration: select your framework explicitly if you rely on the previous default<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"install-ignite-ui-cli-15\" class=\"wp-block-heading\">Install Ignite UI CLI 15<\/h2>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Install globally\nnpm install -g igniteui-cli@15.5.0\n\n# Or run on demand without installing\nnpx igniteui-cli@15.5.0 --help\n<\/pre>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"https:\/\/www.npmjs.com\/package\/igniteui-cli\" rel=\"noopener\"><img decoding=\"async\" src=\"https:\/\/img.shields.io\/npm\/v\/igniteui-cli.svg\" alt=\"igniteui-cli on npm\"\/><\/a><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"ignite-ui-cli-15-faq\" class=\"wp-block-heading\">Ignite UI CLI 15 FAQ<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Does upgrading to Ignite UI CLI 15 break my existing projects?<\/strong><br>\nNo. The 15.0.0 removal of <code>igx-ts-legacy<\/code>, <code>ig-ts<\/code>, and <code>igr-es6<\/code> affects new scaffolding only. Existing projects generated with those types continue to build; you cannot create new projects from them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Which frameworks does the Ignite UI CLI MCP server cover?<\/strong><br>\nAngular, 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Do I need to install the CLI globally to use the MCP server?<\/strong><br>\nNo. Run <code>npx -y igniteui-cli mcp<\/code> to launch the server without a global install. With a global install, <code>ig mcp<\/code> does the same.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Does <code>ai-config<\/code> start the MCP servers for me?<\/strong><br>\nNo. It writes CLI MCP and Theming MCP server entries to <code>.vscode\/mcp.json<\/code> and copies Agent Skills, but you start each server in your AI client. Claude Code is the exception &#8211; it starts configured servers automatically on the first tool invocation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Which AI clients are supported?<\/strong><br>\nVS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Which Angular version do new scaffolds target?<\/strong><br>\nAngular 22. CLI 15.4.0 updated <code>igniteui-angular<\/code> and <code>@angular\/core<\/code> to ~22.0.0 across CLI templates and schematics.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"get-started-with-ignite-ui-cli-15\" class=\"wp-block-heading\">Get Started with Ignite UI CLI 15<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Scaffold a project, run <code>ai-config<\/code>, and start the MCP server in your AI client to work against grounded Ignite UI documentation.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button is-style-fill\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.infragistics.com\/ai-assisted-app-development\">Get Started -&gt;<\/a><\/div>\n\n\n\n<div class=\"wp-block-button is-style-outline is-style-outline--1\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/github.com\/IgniteUI\/igniteui-cli\/releases\" rel=\"noopener\">Full Release Notes<\/a><\/div>\n\n\n\n<div class=\"wp-block-button is-style-outline is-style-outline--2\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/github.com\/IgniteUI\/igniteui-cli\/issues\" rel=\"noopener\">Join the Discussion<\/a><\/div>\n<\/div>\n\n\n<p><!--\nSTRUCTURED_RELEASE_METADATA\nproduct: Ignite UI CLI\nversion: 15.5.0 (release line 15.0.0-15.5.0)\nrelease_date: 2026-07-15\nframework: Angular, React, Web Components, Blazor\npackage_manager: npm\npackage_name: igniteui-cli\ninstall_command: npm install -g igniteui-cli@15.5.0\nchangelog_url: https:\/\/github.com\/IgniteUI\/igniteui-cli\/releases\ndocs_url: https:\/\/www.infragistics.com\/ai-assisted-app-development\nnew_components: []\nnew_features: [IgniteUICLIMCPServer, AiConfigCommand, BlazorProjectScaffolding, EmptyIgbProjectTemplate, SideNavMiniTemplate, AngularTemplateModernization, Angular22Templates, ImprovedMCPSearchRanking, UpdatedWCReactPackageVersions]\nbreaking_changes: true\nbreaking_change_summary: Legacy project types removed (igx-ts-legacy, ig-ts, igr-es6); default framework in step-by-step guide changed from jQuery to Angular\nmin_framework_version: not specified - verify Node.js requirement in the repository README before publish\ntags: [cli, mcp, agent-skills, ai-assisted-development, angular, react, web-components, blazor, scaffolding]\nfaq_section: true\nEND_METADATA\n--><\/p>\n<p><!--\nOPTIONAL FAQPage JSON-LD - use ONLY if Rank Math is not emitting FAQ schema for\nthis post. Emitting both produces duplicate FAQPage nodes.\nPreferred route: Rank Math -> Schema -> add FAQ, mapped to the #ignite-ui-cli-15-faq section.\n\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\"@type\":\"Question\",\"name\":\"Does upgrading to Ignite UI CLI 15 break my existing projects?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"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.\"}},\n    {\"@type\":\"Question\",\"name\":\"Which frameworks does the Ignite UI CLI MCP server cover?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"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.\"}},\n    {\"@type\":\"Question\",\"name\":\"Do I need to install the CLI globally to use the MCP server?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Run npx -y igniteui-cli mcp to launch the server without a global install. With a global install, ig mcp does the same.\"}},\n    {\"@type\":\"Question\",\"name\":\"Does ai-config start the MCP servers for me?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"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.\"}},\n    {\"@type\":\"Question\",\"name\":\"Which AI clients are supported?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.\"}},\n    {\"@type\":\"Question\",\"name\":\"Which Angular version do new scaffolds target?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Angular 22. CLI 15.4.0 updated igniteui-angular and @angular\/core to ~22.0.0 across CLI templates and schematics.\"}}\n  ]\n}\n--><\/p>","protected":false},"excerpt":{"rendered":"<p>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.<\/p>\n","protected":false},"author":22,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[139,141],"tags":[80,82,23,26,150,149,25,122,151,19],"class_list":["post-4065","post","type-post","status-publish","format-standard","hentry","category-ai-engineering","category-ignite-ui-cli-mcp","tag-agent-skills","tag-ai-assisted-development","tag-angular","tag-blazor","tag-ignite-ui-cli","tag-mcp-server","tag-react","tag-release-notes","tag-scaffolding","tag-web-components"],"_links":{"self":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts\/4065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/comments?post=4065"}],"version-history":[{"count":5,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts\/4065\/revisions"}],"predecessor-version":[{"id":4070,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts\/4065\/revisions\/4070"}],"wp:attachment":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/media?parent=4065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/categories?post=4065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/tags?post=4065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}