Telerik Blazor MCP Server

The Telerik Blazor MCP Server enables you achieve interation 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 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.

Prerequisites

To use the Telerik Blazor MCP server, you need:

• A compatible MCP client (IDE, code editor or app) that supports MCP tools.
• A Telerik user account.
• An active DevCraft or Telerik UI for Blazor license or a Telerik UI for Blazor trial.

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-assistant
• Type: stdio (standard input/output transport)
• Command: npx (the MCP server works through an npm package)
• Supported arguments: -y
• npm package name: @progress/telerik-blazor-mcp
• You also need to add your Telerik licence key as an env parameter in the mcp.json file. There are two options:
  • (recommended) 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.

Authentication

The MCP server requires a valid Telerik account with a valid license. In order to get a valid license key check the Telerik Blazor documentation.

To set up the license key, you need to set it up as an environment variable in the JSON configuration file.

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_assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/telerik-blazor-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  }
}

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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/telerik-blazor-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  }
}

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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/telerik-blazor-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      },
    }
  }
}

Usage

To use the Telerik MCP Server:

1. Start your prompt with one of the following:

   • telerik
   • /telerik
   • @telerik
   • telerikblazor
   • /telerikblazor
   • @telerikblazor

2. Confirm that the Telerik MCP server is used, because this doesn't happen deterministically. 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)

   If the Telerik MCP server is not used even though it's installed and enabled, then try rephrasing your prompt and use another trigger syntax from the list in step 1.

3. Grant the Telerik tool a permission to run for this session, workspace, or always.

4. 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 MVC 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.