New to Telerik UI for BlazorStart a free 30-day trial

Telerik UI for Blazor AI Tools Overview

Updated on Feb 27, 2026

The Telerik UI for Blazor AI Tools are delivered through a single Model Context Protocol (MCP) server that connects your AI client to UI-generation capabilities and knowledge specific to Telerik UI for Blazor.

From idea to implementation, you can use the MCP server to generate complete pages, configure components correctly, align with the Progress Design System, and reduce repetitive setup work.

What Are the Telerik UI for Blazor AI Tools

The Telerik Blazor MCP Server is a local MCP server that is distributed through the Telerik.Blazor.MCP NuGet package.

The Telerik Blazor MCP server uses an orchestration-first model, centered on the Agentic UI Generator tool. It contains a core set of specialized assistants. Click the cards below for more details on each assistant:

The Agentic UI Generator orchestrates all assistants so you can build pages and components, apply styling and theming, and stay aligned with the design system in one seamless process. You can use the full end-to-end flow when you need complete page generation, or call a specific assistant directly when you need a focused change.

MCP Server Assistants Diagram

How the Agentic Flow Works

The Agentic UI Generator takes one prompt and manages the flow for you. It decides which assistants to use and combines their output into a single result. Use it when you want to generate a full page quickly, or call a specific assistant when you need a focused update to the layout, components, styling, theme, or icons in your project.

Full Pages

Layout Assistant

Use the Layout Assistant to set up or refine the page structure. It helps with section order, spacing, and responsive behavior so the UI stays clear across desktop, tablet, and mobile.

Typical tasks include adding a new dashboard section, cleaning up visual hierarchy, and converting desktop-first screens into responsive layouts.

Layout Assistant

Component Assistant

Use the Component Assistant when you need help configuring Telerik UI for Blazor components. It helps you pick the right component and wire it correctly with real API patterns.

Common tasks include enabling Grid features (sorting, paging, filtering, grouping), building validated forms, setting up virtual scrolling or export, and using sample data for safe prototyping.

Component Assistant

Styling Assistant

Use the Styling Assistant when you want consistent visuals across the app. It helps define reusable tokens and CSS variables for scalable theming.

Typical tasks include applying brand colors, adding dark mode or high-contrast variants, and keeping styling behavior consistent as new pages are added.

Styling Assistant

Icon Assistant

Use the Icon Assistant to choose icons that match user actions and UI context. This assistant helps you achieve visually consistent navigation, status indicators, and action buttons.

It is useful for toolbars, navigation menus, cards, and any new section where icon consistency matters.

Icon Assistant

Accessibility Assistant

Use the Accessibility Assistant to apply WCAG 2.2 Level AA guidance during implementation, not after it. It helps with ARIA usage, keyboard navigation, and semantic markup. It is especially useful for interactive templates, complex component flows, and final semantic checks before release.

Accessibility Assistant

Validator Assistant

Not designed to be invoked manually. It is called automatically by the UI Generator Orchestrator and ensures the generated code follows Telerik UI for Blazor best practices and standards.

When to Use Orchestrated vs Targeted Mode

Use #telerik_ui_generator for a complete orchestration-first workflow from a single prompt. When you need finer control or want to adjust just one aspect (such as layout, theme, or a component), you can call a specialized assistant directly by its dedicated handle. For details, see Target the Assistants (Advanced).

Start Building in Minutes

To get started with the Telerik Blazor MCP server, complete the following steps:

  1. Configure the MCP server
  2. (Optional) Set up your Telerik license key if not already configured globally
  3. Start prompting in your IDE's chat interface:
    • #telerik_ui_generator for full, orchestrated UI generation
    • #telerik_component_assistant, #telerik_layout_assistant, #telerik_style_assistant, #telerik_icon_assistant, or #telerik_accessibility_assistant for targeted workflows

For detailed setup instructions, see the Installation article. For guided usage, continue with Agentic UI Generator Getting Started.

Example Prompts and Expected Results

The following examples show how natural-language prompts can map to practical, editable output in your project.

prompt
#telerik_ui_generator Build a sales operations dashboard with a pageable and sortable Grid, a monthly revenue Chart, and a KPI summary row.`

Expected result: A page scaffold with responsive sections, configured Telerik UI for Blazor Grid and Chart, both wired to sample data, and KPI cards arranged for desktop and mobile.

prompt
#telerik_ui_generator Apply a dark theme and define reusable CSS variables for brand, surface, and semantic colors.`

Expected result: A token-driven theme setup with color variables and a dark-mode-ready styling baseline that you can refine for your brand.

License Requirements

The Telerik UI for Blazor MCP server and its tools are offered as a single experience through the Agentic UI Generator (#telerik_ui_generator) in all active Telerik subscription licenses.

License TypeAgentic UI Generator
Subscription License
Trial License
Perpetual LicenseNo*

* All AI tools are available with a 30-day AI Tools trial or a Telerik UI for Blazor trial.

Next Steps

See Also