igniteui-theming: Ignite UI themes for an AI agent
igniteui-theming
Infragistics MCP server builds palettes, typography and shadows for Ignite UI components on Angular, React, Web Components, Blazor
- 44 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The server reads project files only to detect the platform and returns code; writing files stays with the agent
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/igniteui-themingDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The server reads project files only to detect the platform and returns code; writing files stays with the agent
This is third-party code. Review the repository files before installing.
What it does
The igniteui-theming package holds the Sass mixins and functions for Ignite UI themes, and it ships an MCP server with 8 tools and 16 resources. detect_platform finds which Ignite UI platform the project uses. create_palette and create_custom_palette calculate color shades, create_typography sets fonts and the type scale, create_elevations configures shadows, and create_theme combines them into a light or dark theme. A second pair of tools works per component: get_component_design_tokens lists the properties of a component that can be changed, and create_component_theme returns ready Sass for the chosen one. Resources carry platform reference data and presets for Material, Bootstrap, Fluent and Indigo. The agent returns theme code for the right platform.
Who it is for. Developers on Angular, React, Web Components and Blazor who use Ignite UI components and need a custom theme instead of the default one
Good fit when
- You need a dark theme in the style of Gruvbox or another palette for an Ignite UI app
- You want a palette with automatic shades from one primary and one secondary color
- You need to learn which design tokens a button or another component has and change its background and text color
- The project moves from one of the Material, Bootstrap, Fluent or Indigo presets to another
- Typography has to be set up for a chosen font and type scale without reading through the wiki
Not a fit when
- The project has no Ignite UI: the server generates code only for Infragistics components
- You need a theme for Tailwind, MUI or another library: the tools are tied to Ignite UI Sass
- You want a finished layout in a graphics editor: the server returns only theme code
- You need a theme for components from other vendors: tokens come only from Ignite UI
Example request
Build a dark Material theme for my Angular app: teal primary color, purple secondary, Inter font.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
The server knows only four Ignite UI platforms: Angular, Web Components, React and Blazor. Check the result against the Infragistics wiki, because some wiki pages are marked as drafts. The server returns the theme code but does not insert it into the project: the agent creates the Sass file as a separate step. There are four presets, and a custom design system needs its tokens set up by hand. The last commit in the repository was made on November 6, 2026.
How to disable. Remove the igniteui-theming entry from the client config, for example with claude mcp remove igniteui-theming. The package in the project and the generated Sass files stay untouched.
FAQ
Which platforms does the server support?
Angular, Web Components, React and Blazor. The detect_platform tool works out which one the project uses.
Do I need to clone the repository?
No. The server ships inside the published igniteui-theming package, and the client starts it through npx. A clone is needed only to run from source.
Where do the preset palettes come from?
From the package itself: Material, Bootstrap, Fluent and Indigo, each with a light and a dark variant. Custom shades come from create_custom_palette.
Does the server change project files?
No, it returns the theme code. The agent makes the file edits, so the result is visible before it is saved.
Where is the server listed in the MCP registry?
As io.github.IgniteUI/igniteui-theming in the official MCP registry; the server.json manifest sits at the repository root.
Discussion
No questions or reviews yet.
Related
MCP serversIgnite UI CLI scaffolds Angular, React and Web Components projects, and ig ai-config sets up MCP servers and skills.
21st.dev MCP server and plugin: search ready React/Tailwind components and logos and generate UI from your agent
An MCP server and plugin to build UI with the agent: curated design systems, UI prompts and layout variations
MCP server of a React component library for agent interfaces: the agent finds a component and adds it to your project
MCP server for the UI Beats catalog of animated React components: search, props, source code and install command for an agent
Preline UI skills for agents: assemble Tailwind CSS component interfaces and generate themes from tokens
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| igniteui-theming: Ignite UI themes for an AI agent (this card) | yes | not required | 44 | |
| Design Systems MCP | no | not required | 227 | a general design-system lookup, while this one generates Sass themes for a single library |
| Shadcn UI MCP Server | no | key is optional | 3,098 | shadcn components on Tailwind, while Ignite UI has its own token system |
README in short
The Infragistics repository is a monorepo of two packages: the igniteui-theming Sass library and the MCP server sources that are built into the published package. The README covers four preset palettes, typography, a shadow scale from 0 to 24 and setup for VS Code, JetBrains, Claude Desktop and Cursor.