Ignite UI Theming MCP Server

What Ignite UI Theming MCP Server MCP server does

Ignite UI Theming MCP Server MCP server connects MCP-compatible AI assistants with the theming capabilities in the igniteui-theming package. It is intended for projects that use Ignite UI components and need generated Sass for visual design foundations or component customization.

The server covers three core theme foundations: color, type, and elevation. It can produce palettes with calculated shades, configure typography with font families and type scales, and create elevation shadows. A complete theme combines those areas into one generated result. The server also exposes component design-token discovery and component-specific theme generation, which helps an assistant identify available customization properties before producing component Sass.

How it works

An MCP client starts the server as a local process and sends tool requests through the Model Context Protocol. The server returns theming results that the assistant can use in its response or incorporate into project files. It does not require the repository to be cloned when the published npm package is used.

The platform-detection tool can identify which Ignite UI platform a project uses. Palette generation supports both automatic shade calculation and more detailed control over individual shades. Typography accepts font-family and type-scale configuration, while elevation configuration covers the available shadow levels. Theme generation combines palette, typography, and elevation settings. Component tools support inspecting design tokens and creating theme code for a selected component.

The underlying package includes presets associated with material, bootstrap, fluent, and indigo themes. Color presets include light and dark variants, and the Sass package can also be imported directly when an application needs only part of the theming library.

Setup and configuration

The published package is installed with:

npm install igniteui-theming

For a package-based MCP configuration, run it with npx:

{
  "command": "npx",
  "args": ["-y", "igniteui-theming"]
}

The repository also contains the MCP source in the packages/mcp workspace. To build from source, install dependencies and run the root build command:

npm install
npm run build

The generated local entry point is packages/theming/dist/mcp/index.js, which can be started with Node. The README documents configuration examples for Claude Desktop, Cursor, VS Code MCP-compatible extensions, and JetBrains AI Assistant. The server is also listed in the MCP Registry as io.github.IgniteUI/igniteui-theming.

Tools and capabilities

Available tools include:

• detect_platform: identifies the Ignite UI platform used by a project.
• create_palette: generates a palette and calculates its shade variations.
• create_custom_palette: creates a palette with individual shade values controlled explicitly.
• create_typography: configures font families and type scales.
• create_elevations: configures elevation shadows.
• create_theme: generates a combined palette, typography, and elevation theme.
• get_component_design_tokens: lists customizable properties for Ignite UI components.
• create_component_theme: generates theme code for a specific component.

Generated Sass can complement direct package usage. For example, the package exposes Sass modules and presets that applications can import with @use, including color, typography, and elevation-related modules.

Limitations and notes

The provided material describes a local, stdio-style process configuration using Node or npx; it does not document a hosted endpoint or environment-variable configuration. The server is packaged alongside the Sass library, so building from source builds both the theming package and MCP output. Client compatibility depends on MCP support; the repository gives specific setup instructions only for the clients named above.