npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@progress/telerik-dpl-mcp

v1.1.3

Published

Model Context Protocol for Telerik Document Processing

Readme

Telerik Document Processing MCP Server

The Telerik Document Processing 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 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: npx (the MCP server works through an npm package)
  • Supported arguments: -y
  • npm package name: @progress/telerik-dpl-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 Purchasing & Licensing 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 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": "npx",
      "args": ["-y", "@progress/telerik-dpl-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  },
  "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": "npx",
      "args": ["-y", "@progress/telerik-dpl-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      }
    }
  },
  "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": "npx",
      "args": ["-y", "@progress/telerik-dpl-mcp@latest"],
      "env": {
        "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
        // or
        "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
      },
    }
  }
}

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.