Ignite UI MCP Server

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/igniteui-mcp-server

About

Use cases: frontend-development, documentation

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

7 read · 0 write · 0 deleteRead-only

Secrets

None asked for

Install scripts

None found

Runs as

Node.js package

Tools (7)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• get_api_referenceread-only

  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="…

• get_docread-only

  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"). For grid feature docs, the bare feature name works without the "grid-" prefix — e.g. "sorting" resolves to "grid-sorting", "remote-data-operations" resolves to "grid-remote-data-operations". Common aliases are also handled: "virtualization" → "grid-virtualization", "virtual-scroll" → "grid-virtualization". For completely unknown names, use list_components or search_docs to discover the exact name fi…

• get_project_setup_guide

  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 respon…

• list_componentsread-only

  Browse the Ignite UI component documentation index for a framework, grouped by the published documentation table of contents. By default returns a compact index: one heading per group with a short group summary and the doc names it contains. Use it to discover what docs exist before calling get_doc. For feature-based or free-text queries ("how do I enable row editing"), use search_docs instead. Narrowing, cheapest first: - 'group' — pass a heading exactly as printed by the index (e.g. "Grids & Lists > Data Grid") to get that group's docs with a summary each, in documentation order. An unknow…

• resolve_importread-only

  Return the exact import statement for Ignite UI symbols — which package and entry point each class, directive, module, service, interface, enum, type or constant must be imported from. Covers angular, react, webcomponents, and blazor. Call this BEFORE writing or fixing import statements. Ignite UI for Angular is split into secondary entry points (e.g. IgxGridComponent → 'igniteui-angular/grids/grid', IgxColumnComponent → 'igniteui-angular/grids/core', IgxButtonDirective → 'igniteui-angular/directives'); guessed paths are a common cause of "has no exported member" / "cannot find module" compil…

• search_apiread-only

  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/direc…

• search_docsread-only

  Full-text search across all Ignite UI documentation for a specific framework. Use this when the user asks "how do I..." or describes a feature need — e.g. "column pinning", "data validation", "virtual scroll", "remote data", "tree*". For browsing by component name instead, use list_components. For a known doc name, use get_doc directly. Returns up to 20 results ranked by relevance — results are title- and keyword-weighted, so the first result is typically the dedicated feature doc for the query. Each result includes: doc name (pass to get_doc for full content), display name, summary, and a t…

Compare and alternatives

• Alternatives to Ignite UI MCP Server →

Featured in

• Best MCP servers for documentation
• Best MCP servers for code generation

Signals

Stars

137

Forks

9

Open issues

4

Contributors

34

Weekly downloads

549

Last commit

Oct 23, 2026 (5 days ago)

Last release

Oct 12, 2026 (16 days ago)

Last package publish

Oct 12, 2026 (16 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.IgniteUI/mcp-server

Version

15.8.2

Auth

No auth

Packages

npm @igniteui/mcp-server

License

MIT

Repository

github.com/IgniteUI/igniteui-cli

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql