Telerik.DPL.MCP 1.1.5

Prefix Reserved
{
  "servers": {
    "Telerik.DPL.MCP": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.DPL.MCP@1.1.5", "--yes"]
    }
  }
}
                    
This package contains an MCP Server. The server can be used in VS Code by copying the generated JSON to your VS Code workspace's .vscode/mcp.json settings file.
dotnet tool install --global Telerik.DPL.MCP --version 1.1.5
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local Telerik.DPL.MCP --version 1.1.5
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Telerik.DPL.MCP&version=1.1.5
                    
nuke :add-package Telerik.DPL.MCP --version 1.1.5
                    

Telerik Document Processing MCP Server

The Telerik Document Processing MCP Server enables you to achieve integration with your already existing AI workflows and reach new levels of developer productivity. The MCP server provides proprietary context to AI-powered IDEs, apps and tools. You can use the MCP server for Document Processing code generation and successfully prompt more complex questions and tasks, and generate tailored code that includes the Telerik Document Processing Libraries.

Prerequisites

To use the Telerik Document Processing MCP server, you need:

Installation

Use the documentation of your AI-powered MCP client to add the Telerik Document Processing 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 Document Processing MCP server are:

  • Server name: telerik-dpl-assistant

  • Type: stdio (standard input/output transport)

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

  • Supported arguments: --yes

  • nuget package name: Telerik.DPL.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.DPL.MCP
MCP Configuration for .NET 8 & 9 Local Tools

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

{
  "servers": {
    "telerik-dpl-assistant": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["tool", "run", "telerik-dpl-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 Purchasing & Licensing documentation.

Configuration Examples

Visual Studio

Refer to Use MCP servers in Visual Studio.

To enable the Telerik Document Processing MCP server in a specific solution, add a .mcp.json file at the root of the solution:

.mcp.json at the solution root

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

VSCode - Copilot

Refer to Use MCP servers in VS Code.

To enable the Telerik Document Processing MCP server in a specific workspace, add a .vscode folder with an mcp.json file at the root of the workspace:

.vscode/mcp.json at the workspace root

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

Cursor

Refer to Model Context Protocol.

To enable the Telerik Document Processing MCP server in a specific workspace, add a .cursor folder with an mcp.json file at the root of the workspace.

.cursor/mcp.json at the workspace root

{
  "mcpServers": {
    "telerik-dpl-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.DPL.MCP"]
    }
  }
}

Usage

To use the Telerik Document Processing MCP server:

  1. Start your prompt with #telerik-dpl-assistant to make sure the Copilot chat will call the Telerik Document Processing MCP server. For best results, specify the target framework.

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

    • Running telerik-dpl-assistant (in VS Code)
    • Calling MCP tool telerik-dpl-assistant (in Cursor)

    If the Telerik Document Processing MCP server is not used even though it's installed and enabled, then try rephrasing your prompt.

  3. Grant the Telerik Document Processing MCP server 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 Document Processing MCP Server being used, or to call it without the need to mention "#telerik-dpl-assistant" explicitly, add custom instructions to your AI-powered tool. Here are examples for GitHub Copilot and Cursor.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
1.1.5 265 3/5/2026
1.1.4 137 2/25/2026
1.1.1 198 1/21/2026
1.1.0 93 1/14/2026
1.0.2 207 12/4/2025
1.0.1 298 11/12/2025
1.0.0 276 11/12/2025