Telerik.Reporting.MCP 1.1.5

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:

• A compatible MCP client (IDE, code editor or app) that supports MCP tools.
• A Telerik user account.
• An active DevCraft or Telerik Reporting license or a Telerik Reporting trial.
• .NET 10

Installation

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

• Server name: telerik-reporting-assistant

• Type: stdio (standard input/output transport)

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

• Supported arguments: --yes

• nuget package name: Telerik.Reporting.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.Reporting.MCP

MCP Configuration for .NET 8 & 9 Local Tools

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

{
  "servers": {
    "telerik-reporting-assistant": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["tool", "run", "telerik-reporting-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 Reporting 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-reporting-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.Reporting.MCP", "--yes"]
    }
  },
  "inputs": []
}

VSCode - Copilot

Refer to Use MCP servers in VS Code.

To enable the Telerik Reporting 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-reporting-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.Reporting.MCP", "--yes"]
    }
  },
  "inputs": []
}

Cursor

Refer to Model Context Protocol.

To enable the Telerik Reporting 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-reporting-assistant": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Telerik.Reporting.MCP", "--yes"]
    }
  }
}

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.<br/>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 telerik-reporting-assistant
   • Visual Studio Code: Running telerik-reporting-assistant
   • Cursor: Calling MCP tool telerik-reporting-assistant

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+
• WebFormsWrapper - WebForms Report Viewer (wrapper of the HTML5 Report Viewer)
• MVCWrapper - MVC Report Viewer (wrapper of the HTML5 Report Viewer)
• WinForms - WinForms Report Viewer (native desktop component)
• WPF - WPF Report Viewer (native desktop component)
• WRDHTML5 - Web Report Designer for HTML5
• WRDBlazorWrapper - Web Report Designer for Blazor (wrapper of the HTML5 Report Designer)
• WRDRestService - Web Report Designer REST Service for .NET Framework 4.6.2
• WRDRestServiceCore - Web Report Designer REST Service for .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:

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.

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:

• GitHub Copilot custom instructions
• Cursor rules

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

• AI Coding Assistant Overview
• Telerik Reporting Prompt Library
• For applications using Native Angular Report Viewer see the Kendo UI for Angular MCP Server article.
• For applications using Native Blazor Report Viewer see the Telerik Blazor MCP Server article.