Angular, React, Blazor, Web Components용 Ignite UI 문서, API 레퍼런스 및 스캐폴딩 가이드를 AI 어시스턴트에게 제공합니다.
다른 이름 IgniteUI/igniteui-cli, igniteui-cli, @igniteui/mcp-server
- 스타
- 138
- Tools
- —
- 다운로드, 30일
- 6,538
- 최신 버전
- 15.9.0
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- MIT
Ignite UI MCP란?
Ignite UI은(는) MCP server입니다. Angular, React, Blazor, Web Components용 Ignite UI 문서, API 레퍼런스 및 스캐폴딩 가이드를 AI 어시스턴트에게 제공합니다.
프로젝트 README에서 생성된 요약
Ignite UI MCP server 정보
Angular, React, Blazor 또는 Web Components로 웹 애플리케이션을 구축하는 개발자는 이 MCP server를 사용하여 AI 어시스턴트가 Ignite UI 기술 리소스에 직접 접근할 수 있도록 설정할 수 있습니다. 이 MCP server를 Claude Desktop, Cursor 또는 VS Code와 같은 클라이언트에 연결하면 AI가 수동 검색 없이도 정확한 문서와 API 상세 정보를 가져올 수 있습니다.
이 server는 stdio를 통해 작동하며, 로컬 SQLite 데이터베이스를 사용하거나 --remote flag를 통해 원격 백엔드를 사용하도록 구성할 수 있습니다. 문서 검색, API 레퍼런스 조회, 프로젝트 설정 가이드 검색을 위한 특정 도구를 제공합니다. 사용자는 ig ai-config command를 사용하여 다양한 코딩 어시스턴트 및 에이전트에 필요한 파일을 준비하는 구성 프로세스를 자동화할 수 있습니다.
활용 사례
- 1컴포넌트 문서 검색AI 어시스턴트에게 grid나 accordion와 같은 특정 Ignite UI 컴포넌트에 대한 문서를 찾아달라고 요청합니다.
- 2API 레퍼런스 조회AI 어시스턴트가 코딩을 지원할 수 있도록 특정 클래스나 컴포넌트에 대한 전체 API 레퍼런스를 가져오게 합니다.
- 3프로젝트 설정 지침 확인적절한 CLI 스캐폴딩 또는 NuGet 설정을 사용하여 새 프로젝트를 초기화하는 단계별 가이드를 요청합니다.
- 4사용 가능한 컴포넌트 목록 확인AI에게 특정 프레임워크로 필터링된 모든 사용 가능한 Ignite UI 컴포넌트 목록을 제공하도록 요청합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Ignite UI MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Ignite UI MCP 설치
$ claude mcp add igniteui-cli -- npx -y @igniteui/mcp-serverCursor에 Ignite UI MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": [
"-y",
"@igniteui/mcp-server"
]
}
}
}VS Code에 Ignite UI MCP 설치
.vscode/mcp.json
{
"servers": {
"igniteui-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@igniteui/mcp-server"
]
}
}
}VS Code CLI에 Ignite UI MCP 설치
$ code --add-mcp '{"name":"igniteui-cli","type":"stdio","command":"npx","args":["-y","@igniteui/mcp-server"]}'Claude Desktop에 Ignite UI MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": [
"-y",
"@igniteui/mcp-server"
]
}
}
}Codex에 Ignite UI MCP 설치
$ codex mcp add igniteui-cli -- npx -y @igniteui/mcp-serverCodex config.toml에 Ignite UI MCP 설치
~/.codex/config.toml
[mcp_servers.igniteui-cli] command = "npx" args = ["-y", "@igniteui/mcp-server"]
Gemini CLI에 Ignite UI MCP 설치
$ gemini mcp add -s user igniteui-cli npx -- -y @igniteui/mcp-serverGemini settings.json에 Ignite UI MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": [
"-y",
"@igniteui/mcp-server"
]
}
}
}자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기Ignite UI CLI
Quickly create projects, including Ignite UI for Angular and Ignite UI for Web Components, for a variety of frameworks.
Overview
Features:
- Create project structure
- Add views with Ignite UI components (e.g. Combo, Grid or Chart)
- Add scenario based templates with multiple components (e.g. a dashboard)
- Build and install npm packages
- Select a theme, support for custom themes coming soon
- Step by step guide
Supported frameworks
- Angular
- React
- Web Components
- Blazor
- jQuery
Prerequisites
The repository houses multiple packages and orchestrates building and publishing them with lerna and npm workspaces.
To build the repository locally you only need Node.js (CI uses 24.x and 26.x) and the npm that ships with it. Install the dependencies from the repository root with npm ci, which installs exactly what package-lock.json records. Use npm install only when you are changing dependencies, since it can rewrite the lockfile.
Packages
This monorepo contains several packages that combine into the igniteui-cli:
| Package | Description | Location |
|---|---|---|
| @igniteui/cli-core | Contains the core functionality of the cli tool | packages/core |
| @igniteui/angular-templates | Contains the template definitions for Angular components | packages/igx-templates |
| @igniteui/angular-schematics | IgniteUI CLI implementation to be used with Angular CLI's schematics engine | packages/ng-schematics |
| igniteui-cli | Standalone IgniteUI CLI tool for React, Blazor, Angular, jQuery and Web Components | packages/cli |
| @igniteui/mcp-server | MCP server providing AI assistants with Ignite UI documentation and API reference | packages/igniteui-mcp/igniteui-doc-mcp |
Table of Contents
Installation
Install the npm package as a global module:
npm install -g igniteui-cli
Usage
The main entry point is igniteui and is also aliased as ig. Both can be used interchangeably to call available commands. Check out our Wiki documentation for more details.
Step by step
To get a guided experience through the available options, simply run:
ig

Upon creation, project will be automatically loaded in the default browser.
NOTE: If that doesn't happen the port may be already in use. Ports vary for different project types, see the description for the ig start command for details on default ports.
List the available commands.
ig help
Generating projects and adding components
Create a new project passing name, framework and style theme.
ig new <project name> --framework=<framework> --type=<proj-type> --theme=<theme>
This will create the project and will install the needed dependencies.
Parameters besides name are optional. Framework defaults to "angular", project type defaults to the first available in the framework and theme to the first available for the project. For more information visit ig new Wiki page.
Generate Ignite UI for Angular project
To create a new project with Ignite UI for Angular use ig new by specifying angular as framework, and optionally igx-ts as project type and selecting one of the project templates:
ig new "IG Project" --framework=angular --type=igx-ts --template=side-nav
The project is created with the Angular CLI (ng new, then ng add igniteui-angular), so this needs network access and always installs the project's packages: --skip-install has no effect for Angular projects.
Generate Ignite UI for React project
To create a new project with Ignite UI for React use ig new by specifying react as framework and igr-ts as project type:
ig new "IG Project" --framework=react --type=igr-ts
Generate Ignite UI for Web Components project
To create a new project with Ignite UI for Web Components use ig new by specifying webcomponents as framework:
ig new "IG Project" --framework=webcomponents
Adding components
Once you have created a project, at any point you can add additional component templates using ig add. Running the command without parameters will guide you through the available templates:
ig add
Add a new component or template to the project passing component ID and choosing a name.
ig add <component/template> <component_name>
The ID matches either a component ("grid", "combo", "text-editor", etc) or a predefined template. Predefined templates are framework/project specific and can provide predefined views with either multiple components or fulfilling a specific use case like "form-validation", "master-detail" and so on.
For full list of supported templates in the current project you can simply run ig list command:
ig list
Build and run
ig build
ig start
Configure AI Tooling
Ignite UI provides rich AI assisted development toolchain. To configure Ignite UI AI tooling — MCP servers and AI coding skills — run:
ig ai-config
You will be prompted with two selections:
- AI agents — which tools to generate skill and instruction files for (Generic and Claude are selected by default)
- Coding assistants — which assistants to configure MCP servers for (general
.mcp.jsonis selected by default, compatible with Claude Code, VS Code, and others)
You can also pass options directly:
ig ai-config --agents claude copilot generic --assistants vscode cursor
This creates or updates the assistant-specific MCP config file (e.g. .mcp.json, .vscode/mcp.json, .cursor/mcp.json) with entries for the Ignite UI MCP and igniteui-theming MCP servers (existing servers are preserved), copies AI coding skill files from installed Ignite UI packages, and generates agent-specific instruction files (e.g. CLAUDE.md, AGENTS.md).
The ig new command also prompts for AI tool configuration as part of project creation.
MCP Server
The CLI includes a bundled MCP (Model Context Protocol) server that provides AI assistants with Ignite UI documentation search, API reference lookup, and scaffolding guidance for Angular, React, Blazor, and Web Components.
Start the MCP server:
ig mcp
The server runs over stdio and supports the following options:
ig mcp --remote <url> # Use a remote backend instead of the local SQLite database
ig mcp --debug # Enable debug logging to mcp-server.log
Using with AI Assistants
For VS Code, the ig ai-config command handles configuration automatically (see above). For other MCP clients (e.g., Claude Desktop, Cursor), configure them manually:
{
"mcpServers": {
"igniteui-cli": {
"command": "npx",
"args": ["-y", "@igniteui/mcp-server"]
},
"igniteui-theming": {
"command": "npx",
"args": ["-y", "igniteui-theming", "igniteui-theming-mcp"]
}
}
}
In a project that lists igniteui-cli as a dependency, ig ai-config writes "args": ["-y", "igniteui-cli", "mcp"] instead, which starts the server bundled with the project's CLI. Use that form there too when configuring manually: with pnpm, npx -y @igniteui/mcp-server cannot start inside such a project.
The first start downloads the server into the npx cache, which can take 10 seconds or more, and npx downloads it again after each new release. If your MCP client has a short connection timeout, install the server globally (npm install -g @igniteui/mcp-server) and use "command": "igniteui-mcp" with no arguments, or pin a version ("args": ["-y", "@igniteui/mcp-server@<version>"]). Pinned and global installs don't update on their own, so the bundled documentation stays at that version until you change it.
The MCP server exposes the following tools to AI assistants:
| Tool | Description |
|---|---|
list_components |
List available Ignite UI component docs. Filter by framework and optional keyword match against filename, component name, keywords, or summary. |
get_doc |
Return the full markdown content of a specific component doc by name (e.g., grid-editing, accordion). |
search_docs |
Full-text search across Ignite UI docs for a specific framework. Supports prefix matching (e.g., grid*). |
search_api |
Search Ignite UI API entries by keyword, feature name, or partial component name. |
get_api_reference |
Return the full API reference for a specific Ignite UI component or class by exact name. |
get_project_setup_guide |
Returns setup guides for creating a new Ignite UI project. For Angular/React/Web Components: CLI scaffolding instructions. For Blazor: dotnet new + NuGet setup guide. |
Testing with MCP Inspector
To interactively test and debug the MCP server tools:
npx @modelcontextprotocol/inspector ig mcp
Schematics
You can also add Ignite UI for Angular components to your projects by using the igniteui/angular-schematics package. It included schematic definitions for most of the logic present in the igniteui-cli. These can be called in any existing Angular project or even when creating one. You can learn more about the schematics package on from its readme.
Contribution
See the Contribution guide to get started.
Run locally
-
Clone the repository
-
Install dependencies from the repository root with
npm ci(installs exactly whatpackage-lock.jsonrecords, for every workspace package, the MCP server included) -
Build everything from the repository root:
npm run build(compiles the monorepo packages, then builds the MCP server viabuild:mcp) -
Open in Visual Studio Code
There is a predefined launch.config file for VS Code in the root folder, so you can use VS Code View/Debug window and choose one of the predefined actions. These include launching the step by step guide, create new project for a particular framework or add components.
-
Hit Start Debugging/F5
Template smoke test
scripts/smoke-test.sh drives the locally built CLI end to end: it scaffolds a project, adds
every component template into it, installs, and builds. The Jasmine specs under spec/ stub out
PackageManager.installPackages, so they verify that files land on disk but never that the result
installs or compiles — this script covers that gap.
npm run build # required: the script runs your local build, not the published CLI
scripts/smoke-test.sh # angular, react and webcomponents (~20-30 min)
Options:
| Option | Meaning |
|---|---|
-f, --frameworks LIST |
comma separated; default angular,react,webcomponents |
-p, --project ID |
project template to scaffold (default: the framework's own default) |
--all-projects |
scaffold and build every project template, skip component adds |
--templates LIST |
only these component template ids — the fast path when iterating |
--isolate |
one project per component template; slow, use to bisect a failure |
--wizard each|pairs|all |
create the projects through the interactive ig new wizard instead: every answer (each), every pair of answers (pairs) or every combination (all) |
--skip-build |
scaffold and add only |
--keep |
keep the generated projects even when everything passes |
-o, --out DIR |
work directory (default output/smoke, which is gitignored) — wiped on each run, see below |
-j, --jobs N |
frameworks to run in parallel (default 1) |
scripts/smoke-test.sh -f angular --templates grid,combo # quick check, ~2 min
scripts/smoke-test.sh -f angular --all-projects # every Angular project template
scripts/smoke-test.sh -f webcomponents --isolate # bisect which template broke
Per-step logs land in <out>/logs/, and <out>/results.tsv is a machine-readable
framework / step / template / status / seconds table. The script exits non-zero if any step
failed and prints a summary of the failures.
The work directory is deleted and recreated on every run, so the script refuses to touch anything
it cannot show is its own: the filesystem root, your home directory, the repository or any directory
containing it, and any non-empty directory that lacks either the .smoke-test-workdir sentinel it
drops or the results.tsv of an earlier run. Point --out elsewhere, or remove the directory
yourself, if you hit that.
Two things to know if you modify it:
- Call the CLI through
cli, neverpackages/cli/bin/execute.js. The wrapper delegates tonode_modules/igniteui-cliwhenever one resolves inside the current directory, and every project template listsigniteui-clias a devDependency. Angular projects install theirs duringig new(ng addneeds the packages), so through the wrapperig addwould silently switch to the published CLI and its bundled templates.cliloads this checkout'spackages/cli/lib/cli.jsinstead. For the other frameworks, scaffolding with--skip-installstill keepsPackageManager.queuePackagefrom spawning installs, so dependencies are written topackage.jsonand installed once at the end. - Exit codes are not sufficient.
Util.errorlogs and returns without setting one, soig add does-not-exist xexits 0. Each step is judged on its exit code and an error scan of its log and an artifact check.
jQuery and Blazor are opt-in via -f. jQuery has no build script and 13 of its templates pull
ignite-ui-full from the Infragistics ProGet feed, which needs credentials; Blazor needs the .NET
SDK and has no component templates, so only dotnet build runs.
MCP Server development
The MCP server at packages/igniteui-mcp/igniteui-doc-mcp has its own build pipeline, separate from the monorepo. It uses ESM (ES2022, Node16 modules) while the rest of the monorepo uses CommonJS. See DEVELOPMENT.md for the full MCP server development guide.
Build the MCP server (from the repo root, after npm ci):
npm run build:mcp # Compiles the MCP server and copies the SQLite DB into its dist/ (also part of npm run build)
Regenerate API reference data (maintainers only):
The API reference data the server ships (docs/*-api/) is committed, so a normal build needs no submodules. To regenerate it after upstream API changes:
cd packages/igniteui-mcp/igniteui-doc-mcp
npm run build:docs:all # build:docs:angular-api, :wc-api, :react-api and :blazor-api in turn
Test the MCP server locally:
npm run build # includes build:mcp
node packages/cli/lib/cli.js mcp # Start via CLI
# or directly:
node packages/igniteui-mcp/igniteui-doc-mcp/dist/index.js # Start the server
Building the CLI packages for publishing
The CLI does not bundle the MCP server: igniteui-cli depends on @igniteui/mcp-server, which is published from packages/igniteui-mcp/igniteui-doc-mcp alongside the other workspace packages. To build them the way the release workflow does:
npm ci
npm run build-pack # production build of every package, MCP server included; also refreshes the ai-config skills from the doc submodules
npm pack in packages/cli/ and in packages/igniteui-mcp/igniteui-doc-mcp/ then produces the two tarballs; the MCP one contains the documentation database and the API reference data.
Data Collection
The Ignite UI CLI tool uses Google Analytics to anonymously report feature usage statistics and basic crash reports. This data is used to help improve the Ignite UI CLI tools over time. You can opt out of analytics before any data is sent by using
ig config set disableAnalytics true -g
when using the CLI. You can read Infragistics privacy policy at https://www.infragistics.com/legal/privacy.
Ignite UI MCP 질문
Ignite UI MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add igniteui-cli -- npx -y @igniteui/mcp-server를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Ignite UI MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.