Skip to content

Commit 1ff7353

Browse files
kdinevCopilotCopilotCopilotrkaraivanov
authored
feat(skills): adding reference to igniteui-cli mcp (#2207)
--------- Co-authored-by: Copilot <copilot@github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: kdinev <1472513+kdinev@users.noreply.github.com> Co-authored-by: Radoslav Karaivanov <rkaraivanov@infragistics.com>
1 parent 91dd6c2 commit 1ff7353

2 files changed

Lines changed: 102 additions & 0 deletions

File tree

skills/igniteui-wc-choose-components/SKILL.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,26 @@ user-invocable: true
88

99
This skill helps AI agents and developers identify the best Ignite UI components for any UI requirement, then provides direct links to official documentation, usage examples, and API references.
1010

11+
## Prerequisites
12+
13+
- The **Ignite UI CLI MCP server** (`igniteui-cli`) available as a tool provider
14+
15+
> **AGENT INSTRUCTION — MCP Server Setup (REQUIRED)**
16+
>
17+
> Before using the Ignite UI CLI MCP tools, you MUST verify the MCP server is available
18+
> by calling `list_components`. If the tool is not available or the call fails,
19+
> you MUST automatically configure it by following the setup instructions in
20+
> [`reference/mcp-setup.md`](./reference/mcp-setup.md).
21+
>
22+
> After writing the file, inform the user that the MCP server has been
23+
> configured and they may need to reload the editor for the tools to activate.
24+
> Start the MCP server and wait for that MCP server to start before continuing the component-related work.
25+
> Do NOT skip this step or ask the user to do it manually.
26+
27+
## Setting Up the Ignite UI CLI MCP Server
28+
29+
> **Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in [`reference/mcp-setup.md`](./reference/mcp-setup.md).** Read that file for editor-specific configuration steps and verification.
30+
1131
## Before You Answer
1232

1333
- Choose the package before writing imports or install steps.
Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
# Setting Up the Ignite UI CLI MCP Server
2+
3+
> **Part of the [`igniteui-wc-choose-components`](../SKILL.md) skill hub.**
4+
5+
## Contents
6+
7+
- [Setting Up the Ignite UI CLI MCP Server](#setting-up-the-ignite-ui-cli-mcp-server)
8+
- [Contents](#contents)
9+
- [VS Code](#vs-code)
10+
- [Cursor](#cursor)
11+
- [Claude Desktop](#claude-desktop)
12+
- [WebStorm / JetBrains IDEs](#webstorm--jetbrains-ides)
13+
- [Verifying the Setup](#verifying-the-setup)
14+
15+
The Ignite UI CLI MCP server enables AI assistants to discover Ignite UI components, access component documentation, and support related Ignite UI workflows. It must be configured in your editor before these tools become available.
16+
17+
## VS Code
18+
19+
Create or edit `.vscode/mcp.json` in your project:
20+
21+
```json
22+
{
23+
"servers": {
24+
"igniteui-cli": {
25+
"command": "npx",
26+
"args": ["-y", "igniteui-cli", "mcp"]
27+
}
28+
}
29+
}
30+
```
31+
32+
This works whether `igniteui-cli` is installed locally in `node_modules` or needs to be pulled from the npm registry — `npx -y` handles both cases.
33+
34+
## Cursor
35+
36+
Create or edit `.cursor/mcp.json`:
37+
38+
```json
39+
{
40+
"mcpServers": {
41+
"igniteui-cli": {
42+
"command": "npx",
43+
"args": ["-y", "igniteui-cli", "mcp"]
44+
}
45+
}
46+
}
47+
```
48+
49+
## Claude Desktop
50+
51+
Edit the Claude Desktop config file:
52+
53+
- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
54+
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
55+
56+
```json
57+
{
58+
"mcpServers": {
59+
"igniteui-cli": {
60+
"command": "npx",
61+
"args": ["-y", "igniteui-cli", "mcp"]
62+
}
63+
}
64+
}
65+
```
66+
67+
## WebStorm / JetBrains IDEs
68+
69+
1. Go to **Settings → Tools → AI Assistant → MCP Servers**
70+
2. Click **+ Add MCP Server**
71+
3. Set Command to `npx` and Arguments to `-y igniteui-cli mcp`
72+
4. Click OK and restart the AI Assistant
73+
74+
> The `-y` flag skips interactive prompts if `igniteui-cli` is not already installed locally.
75+
76+
## Verifying the Setup
77+
78+
After configuring the MCP server, ask your AI assistant:
79+
80+
> "List all available Ignite UI components"
81+
82+
If the MCP server is running, the `list_components` tool will return all available components for the detected framework.

0 commit comments

Comments
 (0)