Model Context Protocol for Telerik Document Processing
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.
To use the Telerik Document Processing 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 Individual Product containing Telerik Document Processing licence or an Individual Product trial.
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.
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.
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
``json`
{
"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": []
}
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
`json`
{
"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": []
}
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
`json`
{
"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"
},
}
}
}
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.Running telerik-dpl-assistant
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:
* (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.