# Ignite UI MCP Server (npm · @igniteui/mcp-server)

Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding

- Trust score: 77/100 (medium)
- Change this week: +27
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@igniteui/mcp-server`: 77/100 (this document), [markdown](https://verifymcp.io/servers/igniteui-mcp-server/igniteui-mcp-server.md), [page](https://verifymcp.io/servers/igniteui-mcp-server/igniteui-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@igniteui/mcp-server`
- Version: `15.4.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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to IgniteUI/igniteui-cli).
  - License check failed: no license is declared.
  - Actively maintained (last published 18 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/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 2368 tokens (~394/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add igniteui-mcp-server -- npx -y @igniteui/mcp-server
```

### Codex

```bash
codex mcp add igniteui-mcp-server -- npx -y @igniteui/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "igniteui-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@igniteui/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add igniteui-mcp-server --command npx --arg -y --arg @igniteui/mcp-server
```

### Hermes

```yaml
mcp_servers:
  igniteui-mcp-server:
    command: "npx"
    args: ["-y", "@igniteui/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "igniteui-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@igniteui/mcp-server"
      ]
    }
  }
}
```

## 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-08-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 76, +37)

- [security improvement] Install scripts: unverified → pass
- [security improvement] Provenance: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security] The attested source repository moved: IgniteUI/igniteui-cli
- [functional regression] License: unverified → fail
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23

### 2026-08-01 (score 39, +10)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified

### 2026-07-31 (score 29, −21)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 50)

First indexed and scored.

## MCP tools (6)

### `list_components` (~334 tokens)

List all available Ignite UI component documentation entries for a given framework. Optionally filter by keyword matched against filename, component name, keywords, or summary.

Use this to discover what docs exist before calling get_doc — e.g. to browse available grid docs, filter with "grid". For feature-based or free-text queries ("how do I enable row editing"), use search_docs instead.

Returns a formatted list where each entry includes: doc name (pass this as the 'name' parameter to get_doc), display name, summary, and premium status. Without a filter, returns the full catalog for the framework.

No pagination — the full result set is returned in one call.

Input parameters:

- `filter` (string): Keyword to match against filename, component name, keywords, or summary. Case-insensitive substring match. Example: 'grid', 'combo', 'chart'. Omit to return all docs for the framework.
- `framework` (string, required): Ignite UI framework. Detect from user context: Angular (Igx prefix, e.g. IgxGrid) → 'angular', React (Igr prefix, e.g. IgrGrid) → 'react', Blazor (Igb prefix, e.g. IgbGrid) → 'blazor', Web Components…

### `get_doc` (~319 tokens)

Retrieve the full markdown content of one specific Ignite UI component doc by its exact name. The name is kebab-case without the .md extension (e.g. "grid-editing", "combo-overview", "accordion").

Use this after discovering doc names from list_components or search_docs. Do NOT guess doc names — call one of those discovery tools first if the name is unknown.

Returns YAML frontmatter (component, keywords, summary) followed by the complete markdown body with code samples, tables, and links.

Returns isError if the doc name is not found, with a suggestion to use list_components.

Input parameters:

- `framework` (string, required): Ignite UI framework. Detect from user context: Angular (Igx prefix, e.g. IgxGrid) → 'angular', React (Igr prefix, e.g. IgrGrid) → 'react', Blazor (Igb prefix, e.g. IgbGrid) → 'blazor', Web Components…
- `name` (string, required): Exact doc name in kebab-case without the .md extension. Examples: "grid-editing", "combo-overview", "accordion". Get valid names from list_components or search_docs.

### `search_docs` (~383 tokens)

Full-text search across all Ignite UI documentation for a specific framework. Supports prefix matching with trailing * (e.g. "grid*" matches grid, grids, grid-editing) and hyphenated terms (e.g. "grid-editing" matched as a phrase).

Use this when the user asks "how do I..." or describes a feature need — e.g. "column pinning", "data validation", "tree*". For browsing by component name instead, use list_components.

Returns up to 20 results ranked by relevance. Each result includes: doc name (pass to get_doc for full content), display name, summary, and a text excerpt with matching terms highlighted between >>> and <<<.

Query must be non-empty. Special characters are sanitized automatically — only * for prefix matching needs to be passed explicitly.

Input parameters:

- `framework` (string, required): Ignite UI framework. Detect from user context: Angular (Igx prefix, e.g. IgxGrid) → 'angular', React (Igr prefix, e.g. IgrGrid) → 'react', Blazor (Igb prefix, e.g. IgbGrid) → 'blazor', Web Components…
- `query` (string, required): Search query for full-text search. Supports prefix matching with trailing * (e.g. 'grid*' matches grid, grids, grid-editing). Hyphenated terms like 'grid-editing' are matched as phrases. Examples: 'c…

### `get_project_setup_guide` (~347 tokens)

Get the Ignite UI project setup guide for one framework: angular, react, blazor, or webcomponents.

Use this when the user wants to create a new Ignite UI project, needs installation or scaffolding steps, or asks how to set up Ignite UI for a specific framework. Use documentation tools such as list_components or search_api first if you need to identify which components the user plans to use.

Returns documentation text only. For Angular, React, and Web Components, it returns Ignite UI CLI setup and template guidance. For Blazor, it returns dotnet new and NuGet installation guidance. The response may contain one or more markdown guide sections concatenated into a single text result.

This tool is read-only: it does not create files, run commands, detect the current project, or modify the workspace.

Template rule: start with the base template unless the user explicitly needs multiple routed views. Use side-nav only when multi-view routing is actually required.

Input parameters:

- `framework` (string): Ignite UI framework. Detect from user context: Angular (Igx prefix, e.g. IgxGrid) → 'angular', React (Igr prefix, e.g. IgrGrid) → 'react', Blazor (Igb prefix, e.g. IgbGrid) → 'blazor', Web Components…

### `get_api_reference` (~434 tokens)

Look up the full API reference for a specific Ignite UI component or class by exact name. Case-insensitive matching. Covers all four frameworks: angular, react, webcomponents, and blazor.

Use this when you already know the exact component name — from the user's code (e.g. IgxGridComponent, IgrGrid, IgcSelect) or from a previous search_api result. If you only have a keyword or partial name, call search_api first to discover the exact name.

Returns formatted markdown with the class/interface summary, properties (with types and descriptions), methods (with signatures), and events. Use section="properties", "methods", or "events" to retrieve only that section and reduce response size. Defaults to section="all".

Supply member="<name>" (e.g. "checked", "click", "igcChange") to return only a single property/method/event line instead of the full entry — useful when the user is asking about one specific member. Takes precedence over section when both are supplied.

Component name must be ≤128 characters. Returns isError with a suggestion to use search_api if not found, or if a supplied member name does not exist on the component.

Input parameters:

- `component` (string, required): Component or class name (case-insensitive). Use the exact name returned by search_api. Examples: "IgxGridComponent", "IgrGrid", "IgcSelect"
- `member` (string): Optional member name (property, method, or event) to return only that entry instead of the full component. Examples: "checked", "click", "igcChange". Takes precedence over "section" when both are sup…
- `platform` (string, required): Platform to look up: angular, react, webcomponents, or blazor.
- `section` (string): Section to return: "properties" (types and descriptions), "methods" (signatures and docs), "events" (names and descriptions), or "all" (full entry). Defaults to "all". Use a specific section to reduc…

### `search_api` (~310 tokens)

Search Ignite UI API entries by keyword, feature name, or partial component name. Returns up to 10 results ranked by relevance across all four frameworks: angular, react, webcomponents, and blazor.

Use this as the discovery step when the exact component name is unknown — e.g. the user asks about "grid virtualization" or "combo filtering". Also use it to confirm which framework a component belongs to. Do NOT use this if you already know the exact component name — call get_api_reference directly instead.

Each result includes: exact component name, framework tag, API type (class/interface/directive/enum), match count, keyword list, and a content excerpt. Pass the component name and framework from a result to get_api_reference for full details. To reduce response size, use section="properties", "methods", or "events" instead of the default "all".

Always specify `platform` when your target framework is known — this prevents cross-framework API contamination. Omit only when you explicitly need to compare or search across all frameworks at once. Maximum query length is 256 characters.

Input parameters:

- `platform` (string): Limit results to one platform (angular, react, webcomponents, or blazor). Omit to search all platforms simultaneously.
- `query` (string, required): Keyword, feature name, or partial component name. Matches against component names, keywords, API type, and content. Partial names work. Examples: "grid virtualization", "IgxCombo", "drag drop", "sele…

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/igniteui-mcp-server/igniteui-mcp-server#diagnostics

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 39
- 2026-07-31: 29
- 2026-07-30: 50
- 2026-07-28: 50
- 2026-07-27: 50

## Links

- npm package: https://www.npmjs.com/package/@igniteui/mcp-server
- Socket report: https://socket.dev/npm/package/@igniteui/mcp-server
- Repository: https://github.com/IgniteUI/igniteui-cli
- Changelog RSS feed: https://verifymcp.io/servers/igniteui-mcp-server/igniteui-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/igniteui-mcp-server/igniteui-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/igniteui-mcp-server/igniteui-mcp-server