KendoReact MCP Server

The KendoReact 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 KendoReact MCP server to ask about Kendo UI for React components, features, or general usage. You can successfully prompt more complex questions and tasks, and generate tailored code that includes Kendo UI for React components and API.

To use the KendoReact 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 Kendo UI for React license or a Kendo UI for React trial.

Use the documentation of your AI-powered MCP client to add the Kendo React 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 KendoReact MCP server are:

• Server name: kendo-react-assistant
• Type: stdio (standard input/output transport)
• Command: npx (the MCP server works through an npm package)
• Supported arguments: -y
• npm package name: @progress/kendo-react-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.

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

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

Refer to Use MCP servers in VS Code.

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

.vscode/mcp.json at the workspace root

{
  "servers": {
    "kendo-react-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/kendo-react-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  }
}

Refer to Model Context Protocol.

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

.cursor/mcp.json at the workspace root

{
  "mcpServers": {
    "kendo-react-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@progress/kendo-react-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      },
    }
  }
}

To use the Kendo React MCP server:

1. Start your prompt with one of the following:

   • kendo
   • /kendo
   • @kendo
   • kendoreact
   • /kendoreact
   • @kendoreact

   Or if you are using VSCode you can type #kendo_react_assistant to make sure the Copilot chat will call the Kendo React MCP server.

2. Confirm that the Kendo React MCP server is used, because this doesn't happen deterministically. Look for a statement in the output, which is similar to:

   • Running kendo-react-assistant (in VS Code)
   • Calling MCP tool kendo-react-assistant (in Cursor)

   If the Kendo React 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 Kendo React MCP sewrver 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 Kendo React MCP Server being used, or to call it without the need to mention "kendo" explicitly, add custom idea instructions to your AI-powered tool. Here are examples for GitHub Copilot and Cursor.