New to KendoReactStart a free 30-day trial

Installation
Premium

Updated on Jan 14, 2026

The KendoReact AI Tools are delivered through a single MCP (Model Context Protocol) server that automatically provides access to the appropriate level of functionality based on your Telerik license type. Your license determines which specialized tools and orchestrator you can access:

  • Agentic UI Generator—Layout, Component, Styling, and Icon tools with comprehensive orchestrator
  • AI Coding Assistant—Component and Icon tools with component-focused orchestrator

This article provides detailed installation instructions for popular AI-powered IDEs and explains how to configure your Telerik license for authentication.

Prerequisites

To use the KendoReact MCP server, you need:

MCP Server Configuration

Use the documentation of your AI-powered MCP client to add the KendoReact MCP server to a specific workspace or globally. Below you can find installation tips and examples for some popular MCP clients, and instructions for configuring your license key.

Visual Studio Code

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

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

Workspace Configuration

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

json
{
  "servers": {
    "kendo-react-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/kendo-react-mcp@latest"],
      // set any of the `env` parameters below only if you haven't set a license key globally on your machine
      //   "env": {
      //     "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE"
      // or
      //     "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      //   }
    }
  }
}

The server name kendo-react-mcp-server can be changed to a custom value based on your preferences.

Global Configuration

To add the KendoReact MCP server globally for VS Code, run the MCP: Open User Configuration command from the Command Palette and add the above content to the automatically created mcp.json file in your user profile.

Alternatively, manually create an mcp.json file with the above content in your user folder.

Cursor

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

Workspace Configuration

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

json
{
  "mcpServers": {
    "kendo-react-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/kendo-react-mcp@latest"],
      // set any of the `env` parameters below only if you haven't set a license key globally on your machine
      //   "env": {
      //     "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE"
      // or
      //     "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      //   }
    }
  }
}

The server name kendo-react-mcp-server can be changed to a custom value based on your preferences.

Global Configuration

To add the MCP server globally for Cursor, add a .cursor folder with the above mcp.json file in your user folder.

License Key Setup

The KendoReact MCP server requires a valid Telerik license 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 KendoReact Licensing.

Next Steps

Now that the MCP server is installed, choose which tool to explore based on your license access:

See Also