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

Telerik Blazor MCP Server

Updated on Aug 26, 2025

The Telerik Blazor MCP Server lets you interact with AI 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 for Blazor AI code generation and 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.

Prerequisites

To use the Telerik Blazor MCP server, you need:

Node.js 18 or a newer version.
A compatible MCP client (IDE, code editor or app) that supports MCP tools. Using the latest version of the MCP client is highly recommended.
A Telerik user account.
An active DevCraft or Telerik UI for Blazor license or a Telerik UI for Blazor trial.
A Blazor application that includes Telerik UI for Blazor.

Check AI Coding Assistant Overview for more recommendations and usage information.

Installation

There are two ways to install the Telerik Blazor MCP server:

Use a manual approach, which is described below.
Use an automated process provided by the Telerik extensions for Visual Studio and VS Code.

To install the Telerik MCP server manually, use the documentation of your AI-powered MCP client. You can enable the MCP server for specific workspaces or globally. The sections below provide installation tips and examples for some popular MCP clients like Visual Studio, VS Code, and Cursor. The generic settings of the Telerik Blazor MCP server are:

npm package name: @progress/telerik-blazor-mcp
Type: stdio (standard input/output transport)
Command: npx
Arguments: -y
Server name: telerikBlazorAssistant (depends on your preferences)
Your Telerik license key as an env parameter

Do not use hyphens (-) or underscores (_) in the MCP server name in the MCP .json file, due to potential compatibility issues with some MCP clients such as Visual Studio or Windsurf.

Some MCP clients expect the MCP servers to be listed under a servers JSON key, while others expect mcpServers.

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

License Key

To use the Telerik MCP Server, your configuration must provide your Telerik licence key as an env parameter in the MCP .json file. There are two options:

Use a TELERIK_LICENSE_PATH argument and point to your Telerik license file location. This approach is recommended, unless you are sharing your VS Code settings across different computers with different operating systems or user names.
Use a TELERIK_LICENSE argument and paste your Telerik license key. Make sure to update the license key when necessary.

Visual Studio

For detailed instructions, refer to Use MCP servers in Visual Studio. You can also install the Telerik Blazor MCP server through the Telerik UI for Blazor Visual Studio extension.

Early Visual Studio 17.14 versions require the Copilot Chat window to be open and active when you open a solution. Otherwise the Telerik MCP server is not used.

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

.mcp.json

JSON

{
  "servers": {
    "telerikBlazorAssistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/telerik-blazor-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "C:\\Users\\___\\AppData\\Roaming\\Telerik\\telerik-license.txt"
      }
    }
  }
}

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

Once the Telerik MCP server is added, make sure that the telerikBlazorAssistant tool is enabled (checked) in the Copilot Chat window's tool selection dropdown. This dropdown opens when clicking on a wrench icon 🔧 at the bottom of the Copilot Window. The Telerik MCP server may get disabled when starting a new chat, changing threads, or relaunching Visual Studio. This is a known issue with MCP servers in general.

VS Code

For detailed instructions, refer to Use MCP servers in VS Code. You can also install the Telerik Blazor MCP server through the Telerik UI for Blazor VS Code extension.

This section applies to VS Code 1.102.1 and newer versions.

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

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

.vscode/mcp.json

JSON

{
  "servers": {
    "telerikBlazorAssistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/telerik-blazor-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "C:\\Users\\___\\AppData\\Roaming\\Telerik\\telerik-license.txt"
      }
    }
  }
}

To use the Telerik MCP server 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,
}

Cursor

For detailed instructions, refer to Model Context Protocol.

To enable the Telerik MCP Server in a specific workspace, Blazor app, or globally, add a .cursor folder with an mcp.json file at the root of the workspace, app, or your user folder, respectively.

.cursor/mcp.json

JSON

{
  "mcpServers": {
    "telerikBlazorAssistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/telerik-blazor-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "C:\\Users\\___\\AppData\\Roaming\\Telerik\\telerik-license.txt"
      }
    }
  }
}

Usage

By default, MCP clients do not call MCP tools in a deterministic way. Some MCP clients like VS Code allow you to explicitly reference the desired MCP tool in your prompt.

To use the Telerik MCP Server:

Start your prompt with Telerik to make it more likely for the Telerik MCP server to get called. If you are using VS Code, then start your prompt with:
- # and the MCP server name that you used in mcp.json (for example, #telerikBlazorAssistant)
- # and the name of the Telerik Blazor MCP tool (#telerik_blazor_assistant)
Confirm that the Telerik MCP server is used. Look for a statement in the output, which is similar to:
- Running telerik_blazor_assistant (in VS Code)
- Calling MCP tool telerik_blazor_assistant (in Cursor)
Grant the Telerik tool permission to run for the current session, workspace, or always.

Also check the general AI Coding Assistant Recommendations for more usage tips.

To call the Telerik MCP server without the need to type Telerik or #telerikBlazorAssistant explicitly, add custom instructions to your AI-powered tool. Here are examples for GitHub Copilot and Cursor.

Sample Prompts

The following list describes how your prompts may look like. Check the Prompt Library for more examples.

"Telerik Generate a Blazor Grid with sorting and paging enabled. Bind the Grid to a Person model and provide dummy data."
"Telerik Generate a ComboBox for Blazor that shows a list of products. Create a Product class and generate sample data."
"Telerik Show me sample code for a Blazor Grid with virtual scrolling for the rows and columns."

Usage Limits

A Telerik Subscription license is recommended in order to use the Telerik Blazor AI Coding Assistant without restrictions. Perpetual license holders and trial users can make a limited number of requests per year.

Connect to Local AI Model

You can use the Telerik Blazor MCP server with local large language models (LLM). For example, run your local model through Ollama and use a third-party package such as MCP-LLM Bridge to connect the model to the Telerik MCP server. This will allow you to use the Telerik AI Coding Assistant without a cloud-based AI model.