We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Ignite UI Theming

MCP server by Infragistics (IgniteUI)

Generate Sass palettes, typography, elevations and themes for Ignite UI components from your AI assistant.

Runs locally (Runs on your machine: its page has the install command)Runs with npx

Install Ignite UI Theming

Runs on your machine. Your client starts it with this command:

npx -y igniteui-theming

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/ignite-ui-theming

About

Connects an AI assistant to the Ignite UI theming library from Infragistics. It can generate color palettes with shade variations, typography setups, elevations and complete light or dark themes as Sass code, customize components with design tokens, and check colors for accessibility.

It runs locally over stdio as part of the igniteui-theming npm package, started with npx. No sign-in or API key is needed. Node.js is required. The package is MIT licensed.

What you can do

  • Generate color palettes with automatic shade variations
  • Create typography systems and type scales
  • Build complete light and dark themes in Sass
  • Customize components with design tokens
  • Validate colors for accessibility compliance
  • Use material, bootstrap, fluent and indigo presets

Tools

Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.

Example prompts

  • Generate a dark indigo-based Ignite UI palette with Sass output.

  • Create a full light theme for my Ignite UI app using the fluent preset.

  • Set up typography for the material type scale in my project.

  • Check whether my primary and surface colors meet accessibility contrast.

Set up

Every client starts Ignite UI Theming on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio ignite-ui-theming -- npx -y igniteui-theming
  1. Start Claude Code and type /mcp. ignite-ui-theming should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "ignite-ui-theming": {
      "command": "npx",
      "args": [
        "-y",
        "igniteui-theming"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "ignite-ui-theming": {
      "command": "npx",
      "args": [
        "-y",
        "igniteui-theming"
      ]
    }
  }
}

Needs Node.js on your computer.

VS Code

Or from a terminal:

code --add-mcp '{"name":"ignite-ui-theming","type":"stdio","command":"npx","args":["-y","igniteui-theming"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "ignite-ui-theming": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "igniteui-theming"
      ]
    }
  }
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "ignite-ui-theming": {
      "command": "npx",
      "args": [
        "-y",
        "igniteui-theming"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add ignite-ui-theming -- npx -y igniteui-theming

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.ignite-ui-theming]
command = "npx"
args = ["-y", "igniteui-theming"]

Needs Node.js on your computer.

Gemini CLI

gemini mcp add ignite-ui-theming npx -- -y igniteui-theming

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

Embed

Show Ignite UI Theming in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Ignite UI Theming on mcp.tc](https://mcp.tc/i/ignite-ui-theming/badge.svg)](https://mcp.tc/i/ignite-ui-theming)
HTML
<a href="https://mcp.tc/i/ignite-ui-theming"><img src="https://mcp.tc/i/ignite-ui-theming/badge.svg" alt="Ignite UI Theming on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/ignite-ui-theming.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/ignite-ui-theming" title="Ignite UI Theming on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/ignite-ui-theming.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Ignite UI Theming card to your site.

Markdown
Add the mcp.tc card for Ignite UI Theming, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/ignite-ui-theming.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="ignite-ui-theming"><a href="https://mcp.tc/i/ignite-ui-theming">Ignite UI Theming on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Ignite UI Theming on mcp.tc](https://mcp.tc/i/ignite-ui-theming/badge.svg)](https://mcp.tc/i/ignite-ui-theming)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow Ignite UI Theming and we’ll email you when something changes.

  1. , Automatic check

    New version 30.2.0 (was 30.1.0). Read from npm.

  2. , Automatic check

    New version 30.1.0 (was 30.0.0). Read from npm.

  3. , Automatic check

    New version 29.1.1 (was 29.1.0). Read from npm.

  4. , Automatic check

    Tracking started: version 29.1.0.

FAQ

Can I paste mcp.tc/i/ignite-ui-theming into my MCP client?

No. Ignite UI Theming runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y igniteui-theming.

Does Ignite UI Theming need an API key?

No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.

Is Ignite UI Theming a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y igniteui-theming, which needs Node.js.

What can Ignite UI Theming do?

You can generate color palettes with automatic shade variations, create typography systems and type scales and build complete light and dark themes in Sass.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to Ignite UI Theming?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Ignite UI Theming’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Infragistics (IgniteUI). This page was built from Ignite UI Theming’s public metadata, last checked on 4 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.