Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/ignite-ui-mcp-server/issues.md or /mcp/ignite-ui-mcp-server/issues.json, or Pod over MCP.

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.

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 · 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 · 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 · 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 · 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 · 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 · 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, cell values in a `bodyT

Read the thread · 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 · 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 · 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

Read the thread · 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: `