Ignite UI

listing.by

Give AI assistants Ignite UI documentation, API reference and CLI project scaffolding for Angular, React and Web Components.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

npx -y @igniteui/mcp-server

listing.local.needs listing.local.note

act.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/ignite-ui

listing.about

Connects an AI assistant to Ignite UI resources: product documentation, API reference and the Ignite UI CLI scaffolding workflow. It helps with building apps that use Ignite UI components for frameworks such as Angular, React and Web Components.

Runs locally over stdio from the npm package @igniteui/mcp-server, started with npx. No API key or environment variables are listed. The server lives in the IgniteUI/igniteui-cli repository, and running ig ai-config in that CLI can generate MCP configuration for supported coding assistants.

listing.can

  • Look up Ignite UI documentation
  • Browse Ignite UI API reference
  • Scaffold Ignite UI projects through the CLI
  • Add components and templates to an existing project

listing.tools

listing.notools.local

listing.prompts

  • How do I configure paging on the Ignite UI Angular grid?

  • Create a new Ignite UI for React project with the CLI.

  • Show the API reference for the Ignite UI combo component.

  • Add a master-detail view to my Ignite UI Angular app.

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio ignite-ui -- npx -y @igniteui/mcp-server
  1. Start Claude Code and type /mcp. ignite-ui should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "ignite-ui": {
      "command": "npx",
      "args": [
        "-y",
        "@igniteui/mcp-server"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Needs Node.js on your computer.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

code --add-mcp '{"name":"ignite-ui","type":"stdio","command":"npx","args":["-y","@igniteui/mcp-server"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "ignite-ui": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@igniteui/mcp-server"
      ]
    }
  }
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "ignite-ui": {
      "command": "npx",
      "args": [
        "-y",
        "@igniteui/mcp-server"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add ignite-ui -- npx -y @igniteui/mcp-server

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.ignite-ui]
command = "npx"
args = ["-y", "@igniteui/mcp-server"]

Needs Node.js on your computer.

Gemini CLI

gemini mcp add ignite-ui npx -- -y @igniteui/mcp-server

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

listing.faq

Can I paste mcp.tc/i/ignite-ui into my MCP client?

No. Ignite UI runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @igniteui/mcp-server.

Does Ignite UI need an API key?

No. It doesn't declare any keys or environment variables. It runs with your user account's permissions, so check what its tools can reach.

Is Ignite UI a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @igniteui/mcp-server, which needs Node.js.

What can Ignite UI do?

You can look up Ignite UI documentation, browse Ignite UI API reference and scaffold Ignite UI projects through the CLI.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Ignite UI's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Ignite UI on mcp.tc](https://mcp.tc/i/ignite-ui/badge.svg)](https://mcp.tc/i/ignite-ui)
HTML
<a href="https://mcp.tc/i/ignite-ui"><img src="https://mcp.tc/i/ignite-ui/badge.svg" alt="Ignite UI on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/ignite-ui.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/ignite-ui" title="Ignite UI on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/ignite-ui.json

listing.em.fields

listing.related

listing.more_in

  • Ignite UI Theming

    Infragistics (IgniteUI)

    state.local.label (state.local.title)

    Generate Sass palettes, typography, elevations and themes for Ignite UI components from your AI assistant.

    mcp.tc/i/ignite-ui-theming

  • SAP Fiori

    SAP

    state.local.label (state.local.title)

    Support SAP Fiori application development from your AI assistant using the SAP Open UX Tools project.

    mcp.tc/i/sap-fiori

  • Awesome Copilot

    Microsoft

    state.local.label (state.local.title)

    Retrieve GitHub Copilot customization files from the Awesome Copilot repository, such as prompts, instructions and chat modes.

    mcp.tc/i/awesome-copilot

  • CAP (SAP Cloud Application Programming Model)

    SAP (cap-js)

    state.local.label (state.local.title)

    Search CDS model definitions and CAP documentation to help AI assistants build SAP CAP applications.

    mcp.tc/i/cap-sap-cloud-application-programming-model

  • UI5

    Developer Tools

    state.local.label (state.local.title)

    Scaffold UI5 apps, lint code, validate manifests and fetch UI5 API docs and guidelines from your AI assistant.

    mcp.tc/i/ui5

  • Arm

    Developer Tools

    state.local.label (state.local.title)

    Search Arm documentation, scan code for Arm compatibility, check container architectures and analyze assembly performance.

    mcp.tc/i/arm

listing.disclaimer_checked