New to Telerik UI for Blazor? Start a free 30-day trial

Installing the Telerik Blazor MCP Server

Updated on Feb 27, 2026

The Telerik UI for Blazor AI Tools are delivered through a single MCP (Model Context Protocol) server. Once configured and authenticated, you can use the Agentic UI Generator tool (#telerik_ui_generator) together with the available specialized MCP assistants.

This article provides detailed installation instructions for popular AI-powered IDEs.

Prerequisites

To use the Telerik Blazor MCP server, you need:

A compatible MCP client (IDE, code editor, or app) that supports MCP server integrations.
.NET 8 or newer.
Enabled HTTP/2 protocol support on the client device and any firewalls and proxies that may manage the network requests.
A Telerik user account.
An active Telerik license that provides access to the Telerik Blazor MCP server.

Telerik Subscription licenses were introduced in 2025 and they explicitly contain the word "Subscription" in their name, for example:

DevCraft Ultimate Subscription

DevCraft Complete Subscription

DevCraft UI Subscription

Telerik UI for Blazor Subscription

An automatically renewing license is not necessarily a Subscription license. The following licenses are Perpetual and they use a legacy naming scheme. These are not Subscription licenses:

DevCraft Ultimate with Subscription and Ultimate Support

DevCraft Complete with Subscription and Priority Support

DevCraft UI with Subscription and Lite Support

MCP Server Configuration

Use the documentation of your AI-powered MCP client to enable the Telerik MCP Server in a specific workspace or globally. Below you can find installation tips and examples for some popular MCP clients.

Generic Settings of the Telerik Blazor MCP Server

Server name: telerik-blazor-mcp (an arbitrary name that depends on your preferences)
Type: stdio (standard input/output transport)
Command: dnx (the MCP server works through the Telerik.Blazor.MCP NuGet package). The dnx value is valid when setting up the MCP Server on .NET 10. For .NET 8 or 9, see .NET 8 and 9 Local Tool Installation
Supported arguments: --yes
NuGet package name: Telerik.Blazor.MCP

License Key Setup

The Telerik 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 (recommended) or locally in the env configuration of the .mcp.json file.

When you start a new trial, you must update your license key.

If you have already completed the Installation Guide and configured your license key, skip directly to MCP Clients Configuration.

Global License Key Configuration

When the telerik-license.txt license file is in its default location, the MCP server will discover it automatically and authenticate successfully:

Default license file location

JSON

"TELERIK_LICENSE_PATH": "C:\\Users\\YourName\\AppData\\Roaming\\Telerik\\telerik-license.txt"

For detailed instructions on installing and activating your license, see the Telerik License Key article.

Local License Key Configuration

To configure the license key locally, you have to define either one of the following arguments inside the env configuration of the .mcp.json file:

TELERIK_LICENSE_PATH—The full path to your license file location, including the license file name itself.
TELERIK_LICENSE—Paste your license key directly. Make sure to update the license key when necessary.

MCP Clients Configuration

Below you can find installation tips and MCP server configuration for some popular MCP clients.

Visual Studio Visual Studio Code Cursor

Refer to Use MCP servers in Visual Studio.

To enable global automatic discovery of the Telerik MCP Server in Visual Studio, add the .mcp.json file posted below to your user directory (%USERPROFILE%), for example, C:\Users\____\.mcp.json.

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).

.mcp.json

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": []
}

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.

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

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": []
}

Make sure that chat.mcp.enabled is enabled in the VS Code settings.

To use the Agentic UI Generator in all workspaces and apps, make sure that chat.mcp.discovery.enabled is enabled in settings.json.

VS Code settings.json

JSON

{
  // ...
  "chat.mcp.discovery.enabled": true,
}

After adding the configuration, restart your IDE to load the Agentic UI Generator.

Refer to Model Context Protocol, which enables Cursor to connect to external tools.

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

JSON

{
  "mcpServers": {
    "telerik-blazor-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["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"
      //}
    }
  }
}

.NET 8 and 9 Local Tool Installation

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

bash

dotnet tool install Telerik.Blazor.MCP

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": []
}

The command argument value must be dotnet, when you configure the MCP Server for .NET 8 or 9.

Next Steps

Now that the MCP server is installed, continue with the Agentic UI Generator and assistant-specific usage guidance:

Begin with the Getting Started guide and explore the Prompt Library.