Skip to content

Latest commit

 

History

History
77 lines (57 loc) · 1.86 KB

File metadata and controls

77 lines (57 loc) · 1.86 KB

Setting Up the Ignite UI CLI MCP Server

Part of the igniteui-angular-components skill hub.

Contents

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.

VS Code

Create or edit .vscode/mcp.json in your project:

{
  "servers": {
    "igniteui-cli": {
      "command": "npx",
      "args": ["-y", "igniteui-cli@next", "mcp"]
    }
  }
}

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.

Cursor

Create or edit .cursor/mcp.json:

{
  "mcpServers": {
    "igniteui-cli": {
      "command": "npx",
      "args": ["-y", "igniteui-cli@next", "mcp"]
    }
  }
}

Claude Desktop

Edit the Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "igniteui-cli": {
      "command": "npx",
      "args": ["-y", "igniteui-cli@next", "mcp"]
    }
  }
}

WebStorm / JetBrains IDEs

  1. Go to Settings → Tools → AI Assistant → MCP Servers
  2. Click + Add MCP Server
  3. Set Command to npx and Arguments to igniteui-cli@next mcp
  4. Click OK and restart the AI Assistant

Verifying the Setup

After configuring the MCP server, ask your AI assistant:

"List all available Ignite UI components"

If the MCP server is running, the list_components tool will return all available components for the detected framework.