Atlas / MCP servers / igniteui / igniteui-theming

igniteui-themingCAUTION

Name: igniteui-theming
Author: igniteui

mcp/igniteui/igniteui-theming

MCP server by igniteui · Audited 2026-10-12

A set of Sass mixins, functions, and variables used to create themes for a variety of UI frameworks built by Infragistics.

Verdict

CAUTION

Grade

Trust score

83 /100

Exposed tools

14 5r · 9w · 0d

Transport

stdio

License

MIT

Stars

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Ignite UI Theming - from Infragistics

[](https://badge.fury.io/js/igniteui-theming)

The Ignite UI Theming repository collects a set of Sass mixins, functions, and variables used to create themes for a variety of UI frameworks built by Infragistics. The theming package makes it super easy to create palettes, elevations and typography styles for your projects.

Repository Structure

This repository is an npm workspaces monorepo with two packages:

The igniteui-theming package is the only published artifact — it includes both the Sass theming library and the MCP server binary.

The MCP server is also listed in the MCP Registry as io.github.IgniteUI/igniteui-theming. The server.json at the repo root is its registry manifest, published automatically on release.

Common commands from the repo root:

npm install    # install all workspace dependencies
npm run build  # build theming + MCP in dependency order
npm test       # run all tests across both packages
npm run lint   # lint all packages

Palettes

We provide four predefined palettes - material, bootstrap, fluent and indigo that have all the necessary colors along with diffent variants of those colors to make it even easier picking the right one for your case. Here's what they look like:

To access any of the color

Read from source at commit b9cc32ff934eOBSERVED · 2026-10-12

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code (npm)

claude mcp add igniteui-theming -- npx -y [email protected]

Exposed tools (14)

5 read · 9 write · 0 destructive.

Tool	Risk	Description
`create_component_theme`	write
`create_custom_palette`	write
`create_elevations`	write
`create_palette`	write
`create_theme`	write
`create_typography`	write
`detect_platform`	read
`get_chart_series_colors`	read
`get_color`	read
`get_component_design_tokens`	read
`read_resource`	read
`set_roundness`	write
`set_size`	write
`set_spacing`	write

Trust audit

CAUTIONgrade B · trust 83/100 Install with care. The audit found things worth knowing before you trust its output.

Layer	What it checks	Result
L0	Provenance & inventory	PASS
L1	Static analysis of the code	WARN
L2	Instruction surface (what it tells the agent)	FAIL
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: none-observed
Network: none-observed
Shell: declared (2 observation(s))
Dependencies: not all pinned
Secrets in source: found

Findings (15)

HIGHPrompt injection · review.misleading_scope · CWE-94, CWE-1427

.claude/commands/opsx/apply.md

Implement tasks from an OpenSpec change (Experimental)

Why it matters. The package is named 'igniteui-theming' suggesting UI theming functionality, but the commands implement an OpenSpec spec-driven development workflow with no theming-related functionality.

Fix. rewrite it so the instruction says plainly what it does, and asks the user before it acts

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321

packages/mcp/src/knowledge/component-metadata.ts:18

/** Source token: 'componentName.tokenName' */