# Reported issues for Ignite UI Theming MCP Server

Pod holds 9 of 9 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 Theming MCP Server](/mcp/ignite-ui-theming-mcp-server).

## Most discussed

### Cannot run theming MCP

I have tried to use Theming MCP:
Installed Ignite UI CLI: npm install -g igniteui-cli
The I ran: npx igniteui-cli ai-config
But Theming MCP started reporting Errors: 

C:\Users\rmirchev\AppData\Local\npm-cache\_logs\2026-07-01T10_42_48_968Z-debug-0.log
2026-07-01 13:42:49.655 [info] Connection state: Error Process exited with code 1
2026-07-01 13:45:35.221 [info] Stopping server igniteui-theming
2026-07-01 13:45:35.232 [info] Starting server igniteui-theming
2026-07-01 13:45:35.232 [info] Connec

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/589) · 2026-07-01 · closed · external user · 1 comment

### Update Readme proposal

Update readme.md:

Prerequisites
  1. VS Code 1.99+ (Help → About to verify)
  2. GitHub Copilot Chat extension installed

Setup
  1. Add to .vscode/mcp.json (include "type": "stdio")
  2. Save the file (Ctrl+S)
  3. MCP: List Servers → confirm server appears
  4. Click Start or reopen VS Code
  5. Open Copilot Chat → Agent mode → verify tools listed

Troubleshooting
  - Server not appearing: check "type": "stdio" is present, file is saved
  - 404 on npx: package is "igniteui-theming", not "@ign

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/554) · 2026-03-21 · open · external user · 0 comments

### "add Ignite UI Theming MCP" request to copilot failed with 404 error

I tried to add Ignite UI Theming MCP trough copilot request for project: https://github.com/[kdinev/world-order](https://github.com/kdinev/world-order).
After prompting the copilot (Sonnet 4.6): add Ignite UI Theming MCP
I received: Searched for files matching `**/.vscode/*.json`, 4 matches

Searched for files matching `**/mcp.json`, 1 match

Read [](file:///c%3A/GitHub/World%20Order/world-order/.vscode/mcp.json)

Replacing 7 lines with 11 lines in [](file:///c%3A/GitHub/World%20Order/world-orde

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/553) · 2026-03-20 · closed · external user · 0 comments

### [MCP] No design tokens are returned for grid-toolbar

Upon retheming grid and it's toolbar, the MCP returns no design tokens for the grid toolbar.

<img width="352" height="663" alt="Image" src="https://github.com/user-attachments/assets/5403f258-ea35-4798-b3c8-b938afbcfab3" />

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/545) · 2026-03-03 · closed · 0 comments

### [MCP] Selector Mismatch: AI generating tag selectors (igx-date-picker) instead of class selectors for date-picker inside overlay

The AI model is producing an incorrect CSS selector for the flat buttons inside the date-picker component, because the date picker's content is rendered inside an Overlay, the igx-date-picker tag selector is not present in the DOM hierarchy.

The generated code should instead use the .igx-date-picker class selector, which is available in the overlay DOM

Steps to Reproduce
Use the MCP server to style a flat button inside a Date Picker (e.g., "Style the flat button inside the date picker with our

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/540) · 2026-02-24 · closed · outside contributor · 0 comments

### The agent sometimes places @ use rules in the middle of a scss file

Agents not always place @ use rules at the beginning of the file, which results in errors. Agents should be instructed to place the @ use rules before any other rules in the file.

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/539) · 2026-02-24 · closed · 0 comments

### The MCP did not recognize linear progress and returned slider instead

I asked for linear progress bars to be replaced with igx-linearprogress and a theme to be created for it, but the MCP tool returned there's no such component and suggested slider instead:

<img width="289" height="1154" alt="Image" src="https://github.com/user-attachments/assets/d0564c19-edee-4e1d-b218-8350db1586e1" />

<img width="288" height="1128" alt="Image" src="https://github.com/user-attachments/assets/301986c5-5670-4451-86b2-9433e0e0c3bf" />

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/538) · 2026-02-24 · closed · 0 comments

### The MCP fails when I ask an Agent to make visual improvements to a grid and cards with list items inside

The MCP server does not recognize that our list has list items, and error is returned with the list of available components, and then the agent correctly recognizes that the list should be used instead, as a top-level component.

<img width="307" height="1089" alt="Image" src="https://github.com/user-attachments/assets/fb14667c-9083-4329-a7ae-750131be3b0c" />

This is working fine, but it might be an improvement if we also return the child components of components, e.g. list-item, igxCardHeaderT

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/534) · 2026-02-19 · closed · 0 comments

## Most recent

### [SassDoc] - Some items are not documented

Palettes are not documented, while others items are not made private.

[Read the thread](https://github.com/IgniteUI/igniteui-theming/issues/48) · 2022-11-15 · closed · 0 comments

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