AI Coding Assistant

New to Telerik Reporting? Download free 30-day trial

Telerik Reporting MCP Server

The Telerik Reporting MCP (Model Context Protocol) Server enhances your AI-powered development experience by providing specialized context about Telerik Reporting.

This MCP server enables AI-powered IDEs and tools to generate more accurate, tailored code that leverages Telerik Reporting APIs. You can ask complex questions about integrating Telerik Reporting in web applications, request specific implementations, and generate comprehensive code solutions.

Prerequisites

To use the Telerik Reporting MCP Server, you need:

Installation

Install the Telerik Reporting MCP server using npm:

npm i @progress/telerik-reporting-mcp

Configuration

Use these settings when configuring the server in your MCP client:

Setting Value
Package Name @progress/telerik-reporting-mcp
Type stdio (standard input/output transport)
Command npx
Arguments -y
Server Name telerik_reporting_assistant (customizable)

License Configuration

Add your Telerik license key as an environment parameter in your mcp.json file using one of these options:

  • Option 1: License File Path (Recommended)
"env": {
    "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE"
}
  • Option 2: Direct License Key
"env": {
    "TELERIK_LICENSE": "YOUR_LICENSE_KEY_HERE"
}

Option 1 is recommended unless you're sharing settings across different systems. Remember to update your license key when necessary.

Visual Studio

For complete setup instructions, see Use MCP servers in Visual Studio.

Early Visual Studio 17.14 versions require the Copilot Chat window to be open when opening a solution for the MCP server to work properly.

Workspace-Specific Setup:

  1. Add .mcp.json to your solution folder (mind the leading dot '.'):

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

  2. Restart Visual Studio.

  3. Enable the telerik_reporting_assistant tool in the Copilot Chat window's tool selection dropdown.

Global Setup:

Add the .mcp.json file to your user directory (%USERPROFILE%, e.g., C:\Users\{user}\.mcp.json).

Visual Studio Code

For complete setup instructions, see Use MCP servers in Visual Studio Code.

Visual Studio Code 1.102.1 or newer is required to use the Telerik MCP Server

The basic setup in Visual Studio Code follows these steps:

  1. Enable chat.mcp.enabled in Visual Studio Code settings.

  2. Create .vscode/mcp.json in your workspace root (or user folder for global setup):

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

    This enables you to call the MCP Server with the #telerik_reporting_assistant handle. To use a custom handle, change the server name in the mcp.json.

  3. For global discovery, enable chat.mcp.discovery.enabled in settings.json:

    {
"chat.mcp.discovery.enabled": true
}

  4. Restart Visual Studio Code.

Installed Reporting MCP Server in VS Code

Cursor

For complete setup instructions, see Model Context Protocol.

Create .cursor/mcp.json in your workspace root (or user folder for global setup):

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

This enables you to call the MCP Server with the #telerik_reporting_assistant handle. To use a custom handle, change the server name in the mcp.json.

Usage

When switching between tasks and files, start a new session in a new chat window to avoid polluting the context with irrelevant or outdated information.

To use the Telerik Reporting MCP Server:

  1. Choose your preferred mode and model.
    At the time of publishing, Claude Sonnet 4 and GPT-5 produce optimal results.

  2. Start your prompt with #telerik_reporting_assistant (or with '#' followed by your custom MCP server name, if set):

  3. Inspect the output and verify that the MCP server is used. Look for messages similar to the ones below:

    • Visual Studio: Running telerikReportingAssistant
    • Visual Studio Code: Running telerik_reporting_assistant
    • Cursor: Calling MCP tool telerikReportingAssistant

  4. If the Telerik Reporting MCP server is not used even though it's installed and enabled, double-check the server name in your configuration and try rephrasing your prompt.

  5. If requested, grant the Telerik Reporting MCP Server permissions to run for this session, workspace, or always.

  6. Start fresh sessions for unrelated prompts to avoid context pollution.

Improving Server Usage

Determining the Reporting Area: To better specify the context for each prompt, the MCP Server will attempt to determine the Telerik Reporting Area the prompt relates to. These areas represent the supported web frameworks and backend technologies, as listed below as pairs consisting of identifier and description:

  • AngularWrapper - Angular Report Viewer (wrapper of the HTML5 Report Viewer)
  • NativeAngular - Native Angular Report Viewer (built with Kendo UI for Angular)
  • BlazorWrapper- Blazor Report Viewer (wrapper of the HTML5 Report Viewer)
  • NativeBlazor - Native Blazor Report Viewer (built with Telerik UI for Blazor)
  • HTML5 - HTML5 Report Viewer (built with Kendo UI for jQuery)
  • React - React Report Viewer (wrapper of the HTML5 Report Viewer)
  • RESTService - Reporting REST Service for .NET Framework
  • RESTServiceCore - Reporting REST Service for .NET Core/.NET 8+
  • General - General question

If the Reporting Area cannot be determined automatically, the MCP Server will display a dialog asking to pick the corresponding area in which the prompt falls in:

A notification requesting input for the Reporting Area of the asked question

After clicking on 'Respond' button, the MCP Server will display a drop-down list with all the areas and wait for selecting the corresponding Reporting Area. If there is no applicable entry, please select 'General' entry at the end of the list.

Select a Reporing Area from the dropdown

Custom Instructions: To increase the likelihood of the Telerik MCP server being used, or to call it without the need to mention "telerik-reporting" explicitly, add custom instructions to your AI tool:

Sample Prompts

The following examples demonstrate useful prompts for the Telerik Reporting MCP Server:

  • "#telerik_reporting_assistant Add a Telerik Report Viewer to my native Angular application."
  • "#telerik_reporting_assistant Connect the Telerik Report Viewer to my Telerik Report Server instance."

Visit the Telerik Reporting Prompt Library for more sample prompts.

Usage Limits

A Telerik Subscription license is recommended in order to use the Telerik Reporting AI Coding Assistant without restrictions. Perpetual license holders and trial users can make a limited number of requests per year.

Connect to Local AI Model

You can use the Telerik Reporting MCP server with local large language models (LLMs):

  1. Run a local model, for example, through Ollama.
  2. Use a bridge package like MCP-LLM Bridge.
  3. Connect your local model to the Telerik MCP server.

This setup allows you to use the Telerik AI Coding Assistant without cloud-based AI models.

See Also

In this article
Related articles
Not finding the help you need? Improve this article