
Ignite UI Theming MCP Server: Setup for Claude, Cursor and Other Apps
Lets Claude, Cursor and other assistants write Sass and CSS themes for Ignite UI apps: colors, fonts, shadows and component styles.
Ignite UI Theming is a free helper from Infragistics that runs on your computer. Your assistant asks it for palettes, fonts, shadows and component styles, and gets back Sass or CSS to put in your project. It needs no account or API key.
It fits Ignite UI apps on Angular, Web Components, React or Blazor, and also works for plain Sass use. Ask Claude to detect the platform first so the code uses the right paths.
Good for
- Developers building apps with Ignite UI for Angular, React, Web Components or Blazor
- Front-end teams who want a brand palette turned into theme code fast
- Designers handing a color scheme to developers
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install Ignite UI Theming MCP
Claude Code
- 1
Copy this prompt.
Add the Ignite UI Theming MCP server to Claude Code. Run this command: claude mcp add ignite-ui-theming -- npx -y igniteui-theming Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
Built from the package data we hold. Not yet tested by us.
Tools
Finds which Ignite UI product your project uses
Looks at your package.json and config files to work out whether the project uses Ignite UI for Angular, Web Components, React or Blazor. The other tools use the answer to pick the right Sass paths.
Try: “Check which Ignite UI platform this project uses before you write any theme code.”
Files ·
detect_platformBuilds a full color palette from a few brand colors
Takes your primary, secondary and surface colors and fills in every shade from lightest to darkest. It returns Sass or plain CSS variables.
Try: “Make a light palette from primary #3F51B5 and secondary #FF4081 as CSS variables.”
Read ·
create_paletteBuilds a palette from shade values you pick
Lets you give every shade of a color yourself instead of having them generated. Use it when a design system already fixes the exact values.
Try: “Build a custom palette from these 14 hex shades of our brand blue.”
Read ·
create_custom_paletteCopies the shade steps of a color ladder you already have
Reads an existing set of shades and works out the lightness curve behind it. You can then reuse that curve for new colors so they step the same way.
Try: “Fit a scale to our existing gray ladder so new palettes match its steps.”
Read ·
fit_color_scaleSets fonts and type sizes for a theme
Writes the font family and type scale setup for your theme, using one of the Material, Bootstrap, Fluent or Indigo presets as a base.
Try: “Set up typography with Inter and the Fluent type scale.”
Read ·
create_typographySets the shadow levels used to lift cards and menus
Produces the shadow setup for the design system you pick, so buttons, cards and menus sit at the right height.
Try: “Generate elevations for the Indigo design system.”
Read ·
create_elevationsWrites a whole theme: palette, type and shadows
Combines palette, typography and elevations into one theme file for light or dark mode. It is the quickest way to start a themed app.
Try: “Create a dark Material theme for my Angular app with primary #1976D2.”
Read ·
create_themeChanges how big controls are, app-wide or per component
Writes the code that switches component size between small, medium and large, either for the whole app or for one component.
Try: “Make the grid use small sizing and leave everything else medium.”
Read ·
set_sizeChanges padding and gaps, app-wide or per component
Writes the code that tightens or loosens the spacing inside components. You can scope it to one component or one CSS selector.
Try: “Loosen spacing on cards by a factor of 1.25.”
Read ·
set_spacingChanges how rounded corners are
Writes the code that sets the corner radius factor, from square to fully round. It works for the whole app or a single component.
Try: “Make all buttons fully rounded but keep inputs square.”
Read ·
set_roundnessLists the style settings a component accepts
Looks up which design tokens a component, such as button or grid, can be styled with. Claude calls it before writing a component theme so it only uses real token names.
Try: “Which tokens can I change on the flat button?”
Read ·
get_component_design_tokensWrites the style code for one component
Generates Sass or CSS that restyles a single component using the tokens you give it, for example a button with a new background and radius.
Try: “Restyle the avatar with a blue background and an 8px radius.”
Read ·
create_component_themeReturns the CSS variable for a palette color
Gives you the exact CSS variable reference for a palette color and shade, such as primary 500, so the code you write stays tied to the theme.
Try: “What is the variable for the primary 300 color?”
Read ·
get_colorReturns the chart color set and checks custom ones
Returns the shared color list used for chart series and the color tokens each chart type uses. It can also check a list of brush colors you supply.
Try: “Which colors does a bar chart use, and does my custom list of five colors work?”
Read ·
get_chart_series_colorsReads the built-in theming reference docs
Opens one of the reference documents bundled with the server, such as platform setup, palette presets, typography presets and layout guidance, by its theming:// address.
Try: “Read the platform setup guide from the theming resources.”
Read ·
read_resource
Read from the source code
Permissions
low risk · 1 thing to watch
Low risk
The tools mostly hand back theme code as text, and detect_platform reads your package.json.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It only returns code and reads your package.json
The tools hand back Sass and CSS text for you or your assistant to paste in. The only project file the code reads is package.json, in detect_platform. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Sign-in and keys | No sign-in or API key. |
|---|
Questions
Is the Ignite UI Theming MCP server official?
Yes. Infragistics, the maker of Ignite UI, ships it inside its own igniteui-theming package and lists it in the MCP Registry as io.github.IgniteUI/igniteui-theming.
Does it need an API key or account?
No. It runs on your computer and needs no sign-in. Add it with the install box above.
Which apps does it work with?
The README gives setup steps for VS Code, JetBrains IDEs, Claude Desktop and Cursor. Any app that can run a local MCP server should also work.
Which Ignite UI platforms does it cover?
Angular, Web Components, React and Blazor, plus a generic mode for plain Sass use. Component-specific tools are not available in generic mode.
Can it change my project files?
Its tools return theme code as text for you or your assistant to place in your project. The one file the code reads is package.json, for platform detection.
Can it run read-only?
There is no read-only switch, and none is needed because the tools only return code.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
igniteui-theming- Registry
- npm
- Transport
- stdio
- Auth
- None
- Version
- 30.0.0
- License
- MIT
- Last commit
- Oct 30, 2026
- Open issues
- 33
- Listed in
- Official MCP registry
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 3Hide
- README.md · github.com
- server.ts · github.com
- descriptions.ts · github.com