Telerik.Blazor.MCP 1.3.0

Telerik Blazor MCP Server

The Telerik Blazor MCP Server enables you to achieve integration with your already existing AI workflows and reach new levels of developer productivity. The MCP server provides proprietary context to AI-powered IDEs, apps and tools. You can use the Telerik Blazor MCP server to ask about Telerik UI for Blazor components, features, or general usage. You can successfully prompt more complex questions and tasks, and generate tailored code that includes Telerik UI for Blazor components and API.

As of version 1.1.2 the Telerik Blazor MCP server automatically recognizes your Telerik license and activates the Agentic UI Generator and the available assistants:

• Agentic UI Generator—Includes all six specialized assistants (Component, Layout, Styling, Icon, Accessibility, and Validator), coordinated by a comprehensive orchestrator designed for complete UI generation.

Agentic UI Generator Intended Use

• Create Individual Components: Build specific Telerik UI for Blazor components with particular configurations and features like filtering, validation, and data binding.
• Create Full Responsive Pages
  • Build complete dashboards, landing pages, and listing pages in existing applications.
  • Generate pages similar to the Progress Design System page templates.
• Modify Existing Pages: Generate new themes inside existing applications. Add dark mode or high-contrast themes.
• Implement Responsive Layout
  • Create new responsive pages and sections.
  • Convert existing pages to be responsive for mobile and tablet views.

Prerequisites

To use the Telerik Blazor MCP server, you need:

• A compatible MCP client (IDE, code editor or app) that supports MCP tools.
• An active Telerik Subscription license that provides access to the Telerik UI for Blazor MCP server.
• .NET 8 or newer

Installation

Use the documentation of your AI-powered MCP client to add the Telerik MCP server to a specific workspace or globally. You can see installation tips and examples for some popular MCP clients below.

The generic settings of the Telerik Blazor MCP server are:

• Server name: telerik-blazor-mcp (depends on your preferences)

• Type: stdio (standard input/output transport)

• Command: dnx (the MCP server works through an nuget package)

• Supported arguments: --yes

• nuget package name: Telerik.Blazor.MCP

• You also need to add your Telerik licence key.

  • Place the file (recommended):
    • on Windows at %AppData%/Telerik/telerik-license.txt;
    • on macOS or linux at ~/.telerik/telerik-license.txt;

  OR alternatively:

  • Use a TELERIK_LICENSE_PATH argument and point to your Telerik license file location.
  • Use a TELERIK_LICENSE argument and paste your Telerik license key. Make sure to update the license key when necessary.

• Some MCP clients expect an mcp.json file, while others like Visual Studio 2022 expect an .mcp.json file.

.NET 8 & 9 Local Tool Installation

For .NET 8 and 9 projects, you can install the MCP server as a local tool without global installation:

dotnet tool install Telerik.Blazor.MCP

MCP Configuration for .NET 8 & 9 Local Tools

For VS Code .vscode/mcp.json using local tools:

{
  "servers": {
    "telerik-blazor-mcp": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["tool", "run", "telerik-blazor-mcp"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  },
  "inputs": []
}

Authentication

The Telerik UI for Blazor MCP server requires an active Subscription or trial license and a valid key for authentication. You can configure your license key either globally on your machine or locally in the .mcp.json configuration file.

• (Recommended) When set globally, the MCP server automatically recognizes the license and you can ignore the env parameter in the .mcp.json setup.
• When configured locally, you have to define either one of the following variables inside the mcp.json file:
  • TELERIK_LICENSE_PATH—to point to your license file location.
  • TELERIK_LICENSE—to paste your license key directly.

For detailed instructions on obtaining and managing your license key, see Telerik UI for Blazor Licensing.

Configuration Examples

Visual Studio

Refer to Use MCP servers in Visual Studio.

To enable the Telerik MCP Server in a specific Blazor app, add a .mcp.json file to the solution folder.

SOLUTIONDIR/.mcp.json

{
  "servers": {
    "telerik-blazor-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.Blazor.MCP", "--yes"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  },
  "inputs": []
}

• 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 in Visual Studio.

VSCode - Copilot

Refer to Use MCP servers in VS Code.

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

.vscode/mcp.json at the workspace root

{
  "servers": {
    "telerik-blazor-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.Blazor.MCP", "--yes"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  },
  "inputs": []
}

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.

.cursor/mcp.json at the workspace root

{
  "mcpServers": {
    "telerik-blazor-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.Blazor.MCP"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  }
}

Usage

To increase the probability of the Telerik UI for Blazor MCP Server being used, or to call it without the need to mention "telerik" explicitly, add custom idea instructions to your AI-powered tool. Here are examples for GitHub Copilot and Cursor.

Agentic UI Generator

To use the Agentic UI Generator mode:

1. Open the AI chat interface in your IDE—Start a new chat session to begin interacting with the Agentic UI Generator.
2. Start your prompt with #telerik_ui_generator (the main MCP tool to start the agentic workflow in the Agentic UI Generator).
3. This will trigger an agentic workflow using the other available MCP tools to retrieve relevant context based on your prompt.
4. Inspect the output and verify that the Telerik Blazor MCP Server is used. Look for a statement in the output, which is similar to:
   • Running telerik_ui_generator (in VS Code)
   • Calling MCP tool telerik_ui_generator (in Cursor)
5. If requested, grant the Telerik Blazor MCP server a permission to run for this session, workspace, or always.

For more information on how to use the Agentic UI Generator see:

• Getting Started
• Prompt Library

General Tips

• If you want to prompt for information or code that are not related to your previous prompts, it is a good practice to start a new session in a new chat window, so that the context is not polluted by irrelevant old information.
• To increase the probability of the Telerik Blazor MCP Server being used, or to call it without the need to mention "telerik" explicitly, add custom instructions to your AI-powered tool. Here are examples for GitHub Copilot and Cursor.