# Ignite UI Theming MCP Server (npm · igniteui-theming)
Generate Sass palettes, typography, elevations, and themes for Ignite UI components.
- Trust score: 92/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20
## Components
- npm · `igniteui-theming`: 92/100 (this document), [markdown](https://verifymcp.io/servers/igniteui-igniteui-theming/igniteui-theming.md), [page](https://verifymcp.io/servers/igniteui-igniteui-theming/igniteui-theming)
## Channel facts
- Registry: `npm`
- Package: `igniteui-theming`
- Version: `29.0.0`
- Transport: `stdio`
## Trust breakdown
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)
Scored 2026-09-20.
- **Supply Chain Security**: 99/100
- No malware found by supply-chain analysis.
- No known CVEs affecting this package version or its production dependencies.
- No install/post-install scripts declared.
- 37 of 148 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
- Source repository is publicly reachable at the declared URL.
- Cryptographically verified build provenance (signed, bound to IgniteUI/igniteui-theming).
- Clear OSI-approved license (MIT).
- Actively maintained (last published 8 days ago).
- Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
- AI-judged instruction clarity (excellent).
- Context-footprint check failed: tool/resource definitions use about 19941 tokens (~486/item across 41 items; 14 tools + 27 resources), over budget; trim descriptions and params.
- Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).
- 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
## Install
### How do I install the Ignite UI Theming MCP Server server?
Ignite UI Theming MCP Server runs locally as an npm package, launched with npx -y igniteui-theming. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
### Claude
```bash
claude mcp add igniteui-igniteui-theming -- npx -y igniteui-theming
```
### Cursor
```json
{
"mcpServers": {
"igniteui-igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}
```
### VS Code
```json
{
"servers": {
"igniteui-igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}
```
### Codex
```bash
codex mcp add igniteui-igniteui-theming -- npx -y igniteui-theming
```
### opencode
```json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"igniteui-igniteui-theming": {
"type": "local",
"command": [
"npx",
"-y",
"igniteui-theming"
],
"enabled": true
}
}
}
```
### OpenClaw
```bash
openclaw mcp add igniteui-igniteui-theming --command npx --arg -y --arg igniteui-theming
```
### Hermes
```yaml
mcp_servers:
igniteui-igniteui-theming:
command: "npx"
args: ["-y", "igniteui-theming"]
```
### Netclaw
```json
{
"McpServers": {
"igniteui-igniteui-theming": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"igniteui-theming"
]
}
}
}
```
### Vellum
```bash
assistant mcp add igniteui-igniteui-theming -t stdio -c npx -a -y igniteui-theming
```
### Other
```json
{
"mcpServers": {
"igniteui-igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}
```
## Changelog
Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.
### 2026-09-19 (score 92, +1)
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
### 2026-09-17 (score 91, +1)
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
### 2026-09-15 (score 90, +1)
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
### 2026-09-13 (score 89, +1)
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
### 2026-09-12 (score 88, +15)
- [security improvement] Malware scan: unverified → pass
### 2026-09-11 (score 73, −14)
- [security regression] Malware scan: pass → unverified
- [functional] Package version: 28.1.1 → 29.0.0
### 2026-09-09 (score 87, +1)
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability rose 1.
### 2026-09-07 (score 86, +1)
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
## MCP tools (14)
### `detect_platform` (~671 tokens)
Detect Target Platform
Detect the target platform by analyzing dependencies and project config files.
\
Use this tool FIRST before generating any theme code to ensure platform-optimized output.
The detected platform determines the correct Sass module paths and syntax.
Output format ("sass" vs "css") is a separate concern — see the output parameter on each
generation tool. For non-Angular platforms, prefer "css" unless the project has a confirmed
Sass pipeline; use your own file-reading tools or ask the user to confirm before choosing
output: "sass".
\
\
Uses multi-signal detection with confidence scoring:
1\. Ignite UI packages (HIGH - 100): igniteui-angular, igniteui-webcomponents, igniteui-react, IgniteUI.Blazor
2\. Config files (MEDIUM-HIGH - 80): angular.json, vite.config.*, next.config.*, .csproj
3\. Framework packages (LOW - 40): @angular/core, react, lit (fallback only)
4\. Generic fallback: When no Ignite UI product is found, returns "generic" for standalone theming
\
\