# Reported issues for Ignite UI MCP Server

Pod holds 20 of 29 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Ignite UI MCP Server](/mcp/ignite-ui-mcp-server).

## Most discussed

### [CLI MCP] Make `ig ai-config` agent-agnostic instead of hard-coding `.claude/skills`

### Framework

All / Not framework-specific

### Related CLI Command

`ai-config`

### Feature Area

CLI command improvement

### Problem Statement

`ig ai-config` currently treats `.claude/skills` as the default and effectively canonical destination for AI skill files. That is too tool-specific. `.claude` is valid for Claude Code, but the Ignite UI CLI is positioning this as general AI tooling, and projects may use GitHub Copilot, Codex, Cursor, Windsurf, or other assistants with different conv

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1660) · 2026-04-23 · closed · external user · 1 comment

### [CLI MCP] Invalid indicatorTypes values ("RSI, MACD") generated for financial charts

### Ignite UI CLI Version

15.0.0-rc3

### Framework

Angular

### CLI Command

ai-config

### Node.js Version

24.2.0

### Operating System

Windows

### Package Manager

None

### Description

When generating financial charts, `indicatorTypes` is sometimes set to `"RSI, MACD"`, which are not valid enum values and result in a runtime error.

```
Error: Invalid FinancialIndicatorType value: RSI
```

### Steps to Reproduce

1. Generate a financial chart using the following prompt:

### Actual 

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1653) · 2026-04-22 · closed · outside contributor · 1 comment

### [CLI MCP] Invalid chartType enum value ("Bar") generated in category chart

### Ignite UI CLI Version

15.0.0-rc2

### Framework

Angular

### CLI Command

ai-config

### Node.js Version

24.2.0

### Operating System

Windows

### Package Manager

npm

### Description

When generating category charts with Claude Sonnet 4.6, the `chartType` is sometimes set to `"Bar"`, which is not a valid member of the expected enum.

This leads to a runtime error:

`ERROR Error: Invalid CategoryChartType value: Bar

### Steps to Reproduce

1. Generate a cateogry chart using the follwi

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1637) · 2026-04-20 · closed · outside contributor · 7 comments

### [CLI MCP] MCP server generates deprecated Ignite UI React module registrations

**Description:**
When using Claude Sonnet with MCP server for a React app, the generated code includes deprecated module registrations:

```
IgrGridModule.register();
IgrPaginatorModule.register();
```

These are no longer required in recent Ignite UI for React versions.

**Expected:**
Do not include deprecated `.register()` calls.

**Actual:**
Deprecated module registrations are added to the generated code.

**Attachments:**
Prompt: 
[Build a modern enterprise web app.md](https://github.com/use

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1629) · 2026-04-17 · closed · outside contributor · 3 comments

### [CLI MCP] [Angular]: Generated views rely too heavily on grids and lack component variety

### Description
In the Angular CLI MCP output, multiple pages are built mainly as grid-based views even when the requested experience would be better represented with other UI patterns such as cards, progress indicators, lists, alerts, or hierarchical views.

This makes the generated application feel repetitive and less representative of a complete UI composition. In some cases, the selected component type also does not match the requested concept well, such as using a tree/grid-style structure 

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1617) · 2026-04-09 · closed · outside contributor · 2 comments

### [CLI MCP]: Generated app does not consistently prefer Ignite UI components over custom HTML/CSS

### Description
Across the CLI MCP flows for React, Web Components, and Angular, the generated apps use Ignite UI components only partially and still fall back to custom HTML/CSS for many common UI patterns.

This does not appear to be caused by missing components or unclear framework support. In all three cases, suitable Ignite UI components exist for much of the generated UI, but they are not being selected and applied consistently during generation.

As a result, the output is only partially 

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1616) · 2026-04-09 · closed · outside contributor · 1 comment

### React - Incorrect generation of grid column `bodyTemplate` when using the MCP server

**Description:**
When generating a React application from a prompt via the MCP server, grid components with a column `bodyTemplate` are generated incorrectly.

The generated templates access cell values using `ctx.dataContext.rowData[fieldName]`, which does not follow the Ignite UI for React Grid (`IgrGrid`) API.

According to the official `IgrGrid` [documentation](https://www.infragistics.com/products/ignite-ui-react/react/components/grids/data-grid#column-template-api), cell values in a `bodyT

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1602) · 2026-04-02 · closed · outside contributor · 2 comments

### Documentation update

Create page for Ignite UI CLI MCP under AI-ASSITED Development for Angular/Reacr/WebC/Blazor

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1569) · 2026-03-26 · closed · outside contributor · 2 comments

## Most recent

### search_docs MCP tool returns irrelevant results for feature-specific queries (e.g. "virtual scroll")

### Ignite UI CLI Version

N/A

### Framework

Angular

### CLI Command

Other

### Node.js Version

N/A

### Operating System

Windows

### Package Manager

None

### Description

When querying `search_docs` for a specific grid feature, the dedicated feature doc is missing from the top 20 results. Generic grid docs that mention the topic in passing rank higher, causing the agent to loop through multiple tool calls before finding the right doc.

### Steps to Reproduce

1. Connect to the igniteui

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1745) · 2026-07-09 · closed · outside contributor · 0 comments

### Updating mcp configuration using npx ig config

### Ignite UI CLI Version

14.2 to 15.2

### Framework

Angular

### CLI Command

ai-config

### Node.js Version

20+

### Operating System

Windows

### Package Manager

None

### Description

As a user, I have project with installed cli and outdated MCP configuration. I want to update the configuration to latest. I have used "npx igniteui-cli@latest ig ai-config" and "ig ai-config". Finally "npm i -g igniteui-cli"

### Steps to Reproduce

1. npx igniteui-cli@latest
2. npm i -g igniteui-cli
3. 

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1707) · 2026-05-27 · closed · outside contributor · 0 comments

### [CLI MCP] [Blazor]: Setup guidance misses required Ignite UI Blazor runtime script

### Ignite UI CLI Version

15.2.1

### Framework

React, Angular, Web Components, jQuery

### CLI Command

new

### Node.js Version

20.11.0

### Operating System

Windows

### Package Manager

None

### Description

The Ignite UI Blazor setup guidance only mentions adding the required theme CSS, but it does not mention the required Ignite UI Blazor runtime script.

The following script is required for the components to work properly:
`<script src="_content/IgniteUI.Blazor/app.bundle.js"></scrip

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1703) · 2026-05-22 · closed · outside contributor · 0 comments

### [CLI MCP] [Blazor]: Grid generation does not add required grid theme stylesheet

### Ignite UI CLI Version

15.2.0

### Framework

Web Components, jQuery, React, Angular

### CLI Command

new

### Node.js Version

20.11.0

### Operating System

Windows

### Package Manager

None

### Description

When using the CLI MCP to add a Grid to a Blazor application, the required Grid theme stylesheet is not added to the application. Because of this, the Grid is rendered without the expected styles.

The following stylesheet should be added automatically:
`<link href="_content/IgniteU

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1700) · 2026-05-20 · closed · outside contributor · 0 comments

### [CLI MCP] [Blazor]: Grid columns are generated with fixed pixel widths, leaving large empty space in the grid

### Ignite UI CLI Version

15.2.0

### Framework

Web Components, jQuery, React, Angular

### CLI Command

new

### Node.js Version

20.11.0

### Operating System

Windows

### Package Manager

None

### Description

The generated grid always sets exact column widths in pixels. Because the widths are fixed, the columns do not adapt to the available grid space, which often leaves a empty area on the right side of the grid.

### Steps to Reproduce

1. Create or generate a project/component that in

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1696) · 2026-05-20 · closed · outside contributor · 0 comments

### [CLI MCP] [Blazor]: Avatar background is applied with `background` prop instead of the actual avatar background

### Ignite UI CLI Version

15.2.0

### Framework

Web Components, jQuery, React, Angular

### CLI Command

new

### Node.js Version

20.11.0

### Operating System

Windows

### Package Manager

None

### Description

The generated avatar background is not applied correctly. Instead of setting the background on the proper avatar content/background area, the styling is applied directly with `background` prop. This causes the avatar UI to look incorrect and visually inconsistent.

### Steps to Repr

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1695) · 2026-05-20 · closed · outside contributor · 0 comments

### [CLI MCP] Incorrect structure when generating igxIconButton with igx-badge

### Ignite UI CLI Version

15.0.0-rc3

### Framework

Angular

### CLI Command

new

### Node.js Version

24.2.0

### Operating System

Windows

### Package Manager

None

### Description

When generating an icon button with a badge, the badge is sometimes added as a child of `igxIconButton` and a sibling of the icon, instead of being placed in a wrapper alongside the button.

This results in incorrect badge rendering.

<img width="122" height="55" alt="Image" src="https://github.com/user-attach

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1659) · 2026-04-22 · closed · outside contributor · 1 comment

### [CLI MCP] [Angular]: AI app generation uses native <input type="date"> inside igx-input-group instead of Ignite UI date input components

### Description: 

When generating an Angular app through the MCP AI flow, date fields are currently being produced with a native HTML date input inside igx-input-group:

```html
<igx-input-group class="form-group">
  <igx-prefix>
    <igx-icon>date_range</igx-icon>
  </igx-prefix>
  <input
    igxInput
    type="date"
    formControlName="dateOfBirth"
    [class.input-error]="dateOfBirth?.invalid && submitted">
  <label igxLabel>Date of Birth *</label>
</igx-input-group>
```

This should not be

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1655) · 2026-04-22 · closed · external user · 1 comment

### [CLI MCP] Invalid chartType enum value ("Candlestick") generated in financial chart

### Ignite UI CLI Version

15.0.0-rc2

### Framework

Angular

### CLI Command

ai-config

### Node.js Version

24.2.0

### Operating System

Windows

### Package Manager

npm

### Description

When generating financial charts with Claude Sonnet 4.6, the `chartType` is sometimes set to `"Candlestick"`, which is not a valid member of the expected enum.

This results in This leads to a runtime error:

`ERROR Error: Invalid FinancialChartType value: Candlestick`

### Steps to Reproduce

1. Generate

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1647) · 2026-04-21 · closed · outside contributor · 0 comments

### ai-config rewrites mcp.json file if existing

### Ignite UI CLI Version

15.0.0-rc.1

### Framework

Angular

### CLI Command

ai-config

### Node.js Version

v22.18.0

### Operating System

Windows

### Package Manager

npm

### Description

When we have a project created with Angular CLI it creates mcp.json. When we call ai-config to add IgniteUI MCP and Theming MCP the file is overwritten and the Angular MCP is deleted.

### Steps to Reproduce

1. Create a new project with Angular CLI
2. Add igniteui-angular
3.Call ig ai-config

### Act

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1646) · 2026-04-21 · closed · outside contributor · 0 comments

### [CLI MCP]: Generation mixes one library binding patterns with Ignite UI APIs

### Description
In some generated outputs, the code mixes component APIs and binding patterns from different libraries instead of using the conventions of the target library consistently.

This can lead to incorrect behavior such as:

reading values from the wrong event shape
using props or bindings that belong to another framework or component model
combining state patterns that conflict with the target component’s internal behavior
producing code that looks valid at first glance but does not w

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1620) · 2026-04-09 · closed · outside contributor · 1 comment

### [CLI MCP]: Some generated grids are missing explicit height and render too small

### Description
In the generated app, some grid instances are rendered without an explicit height. Because of this, those grids appear too small and do not display as expected.

Grids requires an explicit height for proper rendering. When height is not set, the grid falls back to a minimal calculated height rather than expanding like other table components. This leads to inconsistent results across views, especially when some grids have height defined and others do not.

### Proposed Solution
En

[Read the thread](https://github.com/IgniteUI/igniteui-cli/issues/1619) · 2026-04-09 · closed · outside contributor · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/IgniteUI/igniteui-cli/issues).