Skip to main content
Any Framework

Package Description

Published
Aug 14, 2026
2mo ago
Total Downloads
3.2K
3,182

Install

dotnet add package Telerik.WPF.MCP --version 1.8.0

No framework information available.

README

Telerik WPF MCP Server

The Telerik WPF MCP Server enables you achieve interaction 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 WPF MCP server to ask about Telerik UI for WPF components, features, or general usage. You can successfully prompt more complex questions and tasks, and generate tailored code that includes Telerik UI for WPF components and API.

Prerequisites

To use the Telerik WPF MCP server, you need:

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 WPF MCP server are:

  • Server name: telerik-wpf-assistant

  • Type: stdio (standard input/output transport)

  • Command: dnx (the MCP server works through an nuget package)

  • Supported arguments: -y

  • nuget package name: Telerik.WPF.MCP

  • You also need to add your Telerik licence key.

    • Place the file (recommended):
      • on Windows at %AppData%/Telerik/telerik-license.txt;
      • on macOS or linux at ~/.telerik/telerik-license.txt;

    OR alternatively:

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

.NET 8 & 9 Local Tool Installation

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

dotnet tool install Telerik.WPF.MCP
MCP Configuration for .NET 8 & 9 Local Tools

For VS Code .vscode/mcp.json using local tools:

{
  "servers": {
    "telerik-wpf-assistant": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["tool", "run", "telerik-wpf-assistant"]
    }
  },
  "inputs": []
}

Authentication

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

Configuration Examples

Visual Studio

Refer to Use MCP servers in Visual Studio.

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

SOLUTIONDIR/.mcp.json

{
  "servers": {
    "telerik-wpf-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.WPF.MCP", "--yes"]
    }
  },
  "inputs": []
}

VSCode - Copilot

Refer to Use MCP servers in VS Code.

To enable the Telerik MCP Server in a specific workspace or WPF 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-wpf-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.WPF.MCP", "--yes"]
    }
  },
  "inputs": []
}

Cursor

Refer to Model Context Protocol.

To enable the Telerik MCP Server in a specific workspace or WPF 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-wpf-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.WPF.MCP"]
    }
  }
}

Usage

To use the Telerik MCP Server:

  1. Start your prompt with one of the following:

    • telerik
    • /telerik
    • @telerik
    • telerikwpf
    • /telerikwpf
    • @telerikwpf
  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-wpf-assistant (in VS Code)
    • Calling MCP tool telerik-wpf-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.

Upgrade Assistant

The MCP server includes a telerik-upgrade-assistant tool that analyzes your existing WPF project for breaking changes when upgrading between Telerik UI for WPF versions. The tool integrates with the Telerik CLI (telerik migrate analyze) and returns structured findings that the AI model can use to apply fixes automatically.

How it works

  1. The tool checks if the Telerik CLI is installed globally. If not, it prompts you to install it.
  2. It runs telerik migrate analyze --product wpf against your project and parses the JSON output.
  3. The findings (file, line, member, old/new API signature) are returned to the AI model, which can then apply the necessary code changes.

Example prompts

  • "Upgrade my WPF project to the latest Telerik version and fix breaking changes"
  • "Analyze my project at C:\MyApp\MyApp.csproj for Telerik breaking changes"
  • "I want to upgrade from Telerik 2024.1 to the latest version"

Parameters

Parameter Required Description
projectPath Yes Absolute path to the WPF .csproj file
targetVersion No Telerik version to upgrade to (defaults to latest)
fromVersion No Current Telerik version (auto-detected from project)

Changes from Previous Version

No structural changes between v1.7.0 and v1.8.0.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.