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

Getting Started with the Agentic UI Generator

Updated on May 21, 2026

The Agentic UI Generator is an intelligent development tool delivered through the Telerik Blazor MCP Server that enables UI generation from natural language prompts. Once configured and authenticated, you can use the Agentic UI Generator tool (#telerik_ui_generator) together with the available specialized MCP assistants.

You can get started in two ways:

  • Try it in the browser (no setup required) - the Blazor REPL includes a built-in Agentic UI Generator integration, allowing you to generate, run, and evaluate Telerik UI for Blazor components directly in the browser. To use it, describe your UI requirements using natural language in the REPL's chat interface, and iterate with follow-up prompts. Sign in and get 10 monthly requests to evaluate the Agentic UI Generator without leaving the browser.
  • Set up locally - use the Telerik CLI to configure your local environment, or set it up manually. The Telerik CLI automates license configuration, Telerik MCP server and Telerik NuGet setup, and project scaffolding. Get started in minutes—follow the Quick Start guide to configure your local environment.

Prerequisites

To use the Telerik Blazor MCP server, you need:

Quick Start

Use the Telerik CLI and the built-in Getting Started Assistant to handle the entire setup automatically - whether you are starting a new project or adding Telerik UI for Blazor to an existing one.

Follow these steps to set up the Agentic UI Generator and use it in your IDE:

  1. Install the Telerik CLI globally by executing the following command in any standard command-line interface (CLI) or terminal on your operating system:

    SH
    dotnet tool install -g Telerik.CLI
  2. Configure the Telerik Nuget feed, activate (update) your Telerik license, and set up the Telerik MCP server with the Telerik CLI:

    SH
    telerik setup blazor
    SH
    dotnet tool install Telerik.Blazor.MCP
    SH
    telerik setup blazor
  3. Create a Blank Solution in Visual Studio, or an empty folder in Visual Studio Code, and open it in your IDE. In the AI chat interface, invoke the Getting Started Assistant:

    text
    #telerik_getting_started_assistant create a new blazor web app
  1. Ensure you have a supported license and set up your Telerik license key globally on your machine or in the .mcp.json configuration. The server automatically recognizes your license and activates the available MCP tools.

  2. Create/update the .mcp.json file in the root folder of your solution (if you are using Visual Studio), or the mcp.json file in your workspace (if you are using Visual Studio Code or Cursor):

    For more information about using MCP servers in Visual Studio, refer to Use MCP servers in Visual Studio.

    JSON
    {
      "servers": {
        "telerik-blazor-mcp": {
          "type": "stdio",
          "command": "dnx",
          "args": ["Telerik.Blazor.MCP", "--yes"],
          // set any of the arguments in the 'env' configuration below, if you haven't set up your license file globally 
          //"env": {
          //  "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
          //  // or
          //  "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
          //}
        }
      },
      "inputs": []
    }

    To add the Telerik MCP server globally for Visual Studio, manually create an .mcp.json file with the content posted above in your user folder.

    For more information about using MCP servers in Visual Studio Code, refer to Use MCP servers in VS Code.

    To enable the Telerik MCP Server in a specific in a specific workspace or Blazor app, add a .vscode folder with an mcp.json file at the root of the workspace with the following content:

    JSON
    {
      "servers": {
        "telerik-blazor-mcp": {
          "type": "stdio",
          "command": "dnx",
          "args": ["Telerik.Blazor.MCP", "--yes"],
          // set any of the arguments in the 'env' configuration below, if you haven't set up your license file globally 
          //"env": {
          //  "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
          //  // or
          //  "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
          //}
        }
      }
    }

    To add the Telerik MCP server globally for Visual Studio Code, manually create an mcp.json file with the content posted above in your user folder.

    For more information about using MCP servers in Cursor, refer to Model Context Protocol.

    To enable the Telerik MCP server in a specific workspace or Blazor app, add a .cursor folder with an mcp.json file at the root of the workspace with the following content:

    JSON
    {
      "mcpServers": {
        "telerik-blazor-mcp": {
          "type": "stdio",
          "command": "dnx",
          "args": ["Telerik.Blazor.MCP", "--yes"],
          // set any of the arguments in the 'env' configuration below, if you haven't set up your license file globally 
          //"env": {
          //  "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
          //  // or
          //  "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
          //}
        }
      }
    }

    For .NET 8 and 9 projects, you can install the MCP server as a local tool without global installation. To enable the Telerik MCP Server in a specific Blazor app, add a .mcp.json file to the solution folder (if you are using Visual Studio), or an mcp.json file in your workspace (if you are using Visual Studio Code or Cursor).

    1. Install the Telerik MCP server by executing the following command in any standard command-line interface (CLI) or terminal on your operating system:
    bash
    dotnet tool install Telerik.Blazor.MCP
    1. MCP Configuration for VS Code .vscode/mcp.json using local tools:
    JSON
    {
       "servers": {
          "telerik-blazor-mcp": {
             "type": "stdio",
             "command": "dotnet",
             "args": ["tool", "run", "telerik-blazor-mcp"],
             // set any of the arguments in the 'env' configuration below, if you haven't set up your license file globally 
             //"env": {
             //  "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
             //  // or
             //  "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
             //}
          }
       },
       "inputs": []
    }

    You can customize the server name telerik-blazor-mcp as desired. The name helps distinguish the MCP server in your configuration and does not affect how you invoke the Agentic UI Generator in your prompt.

    Once the Telerik MCP server is added, make sure that all of its tools are enabled (checked) in the Copilot Chat window's tool selection dropdown.

  3. Open the AI chat interface of your IDE and start your prompt with Telerik to make it more likely for the Agentic UI Generator orchestrator to get called. If you are using VS Code, then you can start your prompt with the #telerik_ui_generator handle to invoke the orchestrator:

    TEXT
    #telerik_ui_generator Create a dashboard page with a grid showing sales data and a chart visualizing monthly trends.

Use Cases

The Agentic UI Generator is designed to help with various development scenarios:

  • Generate specific Telerik UI for Blazor components with particular configurations and features like filtering, validation, and data binding.
  • Create full responsive pages
  • Modify existing pages
    • Enhance existing dashboards by adding new sections.
    • Insert new sections that match existing layout style and responsiveness.
  • Create and modify themes
  • Implement Responsive Layout
    • Create new responsive pages and sections.
    • Convert existing pages to be responsive for mobile and tablet views.

For a comprehensive collection of sample prompts covering general UI tasks, layout organization, component implementation, styling, accessibility, and icon selection, see the Agentic UI Generator Prompt Library.

While the Agentic UI Generator performs great with powerful models like Claude Sonnet 4.6, GPT-5.2, or Gemini 3 Pro, it also excels with smaller models as well (such as Haiku and GPT 5.1 mini).

See Also