Ignite UI MCP Server

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="properties", "methods", or "events" to retrieve only that section and reduce response size. Defaults to section="all". Supply member="<name>" (e.g. "checked", "click", "igcChange") to return only a single property/method/event line instead of the full entry — useful when the user is asking about one specific member. Takes precedence over section when both are supplied. Component name must be ≤128 characters. Returns isError with a suggestion to use search_api if not found, or if a supplied member name does not exist on the component.

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 first. Returns YAML frontmatter (component, keywords, summary) followed by the complete markdown body with code samples, tables, and links. Returns isError if the doc name is not found, with a suggestion to use list_components.

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 response may contain one or more markdown guide sections concatenated into a single text result. This tool is read-only: it does not create files, run commands, detect the current project, or modify the workspace. Template rule: start with the base template unless the user explicitly needs multiple routed views. Use side-nav only when multi-view routing is actually required.

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 unknown value returns the valid headings rather than an error. - 'filter' — case-insensitive substring match on filename, component name, keywords, summary, or group name. Groups with no match are omitted; per-doc summaries are included when few enough docs match. Combine with 'group' to search inside one group. - 'detail: "docs"' — the flat per-doc list with a summary for every doc. This is the largest response by a wide margin; reach for it only when you genuinely need every summary at once. It matches the five doc columns only, not group names. Doc names printed by any mode are what you pass as the 'name' parameter to get_doc. ⭐ marks premium docs. No pagination — the full result set is returned in one call.

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" compile errors. React and Web Components symbols are spread over several packages (e.g. igniteui-react-grids, igniteui-webcomponents-grids/grids). For Blazor, returns the NuGet package, the @using namespace and the module registration. Pass every symbol a file needs in one call: symbols=["IgxGridComponent", "IgxColumnComponent"]. The platform is inferred from the Igx/Igr/Igc/Igb prefix; pass `platform` for names without one (e.g. "GridSelectionMode"). Returns ready-to-paste import lines grouped by module, plus "Did you mean" suggestions for names that do not exist (e.g. IgxGrid → IgxGridComponent). Up to 50 symbols per call.

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/directive/enum), match count, keyword list, and a content excerpt. Pass the component name and framework from a result to get_api_reference for full details. To reduce response size, use section="properties", "methods", or "events" instead of the default "all". Always specify `platform` when your target framework is known — this prevents cross-framework API contamination. Omit only when you explicitly need to compare or search across all frameworks at once. Maximum query length is 256 characters.

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 text excerpt with matching terms highlighted between >>> and <<<. Query syntax: multi-word queries require ALL terms to appear (implicit AND) — "virtual scroll" matches docs containing both words. Prefix matching with trailing * (e.g. "grid*"). Hyphenated terms matched as a phrase (e.g. "grid-editing"). Special characters are sanitized automatically — only * needs to be passed explicitly. Query must be non-empty.