Telerik.ASPNETCoreTag.MCP
1.0.1
Prefix Reserved
See the version list below for details.
{ "servers": { "Telerik.ASPNETCoreTag.MCP": { "type": "stdio", "command": "dnx", "args": ["Telerik.ASPNETCoreTag.MCP@1.0.1", "--yes"] } } }
.vscode/mcp.json settings file.
dotnet tool install --global Telerik.ASPNETCoreTag.MCP --version 1.0.1
dotnet new tool-manifest
dotnet tool install --local Telerik.ASPNETCoreTag.MCP --version 1.0.1
#tool dotnet:?package=Telerik.ASPNETCoreTag.MCP&version=1.0.1
nuke :add-package Telerik.ASPNETCoreTag.MCP --version 1.0.1
Telerik ASP.NET CoreTagHelpers MCP Server
The Telerik ASP.NET CoreTagHelpers 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 Telerik ASP.NET CoreTagHelpers MCP server to ask about Telerik UI for ASP.NET Core components, features, or general usage. You can successfully prompt more complex questions and tasks, and generate tailored code that includes Telerik UI for ASP.NET Core components and API.
Prerequisites
To use the Telerik ASP.NET CoreTagHelpers 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 UI for ASP.NET Core license or a Telerik UI for ASP.NET Core trial.
- .NET 10
Installation
Use the documentation of your AI-powered MCP client to add the Telerik 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 ASP.NET Core TagHelpers MCP server are:
Server name:
telerik-aspnetcoretag-assistant(depends on your preferences)Type:
stdio(standard input/output transport)Command:
dnx(the MCP server works through an nuget package)Supported arguments:
--yesnuget package name:
Telerik.ASPNETCoreTag.MCPYou 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;
- on Windows at
OR alternatively:
- Use a
TELERIK_LICENSE_PATHargument and point to your Telerik license file location. - Use a
TELERIK_LICENSEargument and paste your Telerik license key. Make sure to update the license key when necessary.
- Place the file (recommended):
.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.ASPNETCoreTag.MCP
MCP Configuration for .NET 8 & 9 Local Tools
For VS Code .vscode/mcp.json using local tools:
{
"servers": {
"telerik-aspnetcoretag-assistant": {
"type": "stdio",
"command": "dotnet",
"args": ["tool", "run", "telerik-aspnetcoretag-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 Telerik UI for ASP.NET Core documentation.
Configuration Examples
Visual Studio
Refer to Use MCP servers in Visual Studio.
To enable the Telerik MCP Server in a specific ASP.NET Core app, add a .mcp.json file to the solution folder.
SOLUTIONDIR/.mcp.json
{
"servers": {
"telerik-aspnetcoretag-assistant": {
"type": "stdio",
"command": "dnx",
"args": ["Telerik.ASPNETCoreTag.MCP", "--yes"]
}
},
"inputs": []
}
- Once the Telerik MCP server is added, make sure that the telerik-aspnetcoretag-assistant tool is enabled (checked) in the Copilot Chat window's tool selection dropdown in Visual Studio.
VSCode - Copilot
Refer to Use MCP servers in VS Code.
To enable the Telerik MCP Server in a specific workspace or ASP.NET Core app, add a .vscode folder with an mcp.json file at the root of the workspace:
.vscode/mcp.json at the workspace root
{
"servers": {
"telerik-aspnetcoretag-assistant": {
"type": "stdio",
"command": "dnx",
"args": ["Telerik.ASPNETCoreTag.MCP", "--yes"]
}
},
"inputs": []
}
Cursor
Refer to Model Context Protocol.
To enable the Telerik MCP Server in a specific workspace or ASP.NET Core app, add a .cursor folder with an mcp.json file at the root of the workspace.
.cursor/mcp.json at the workspace root
{
"mcpServers": {
"telerik-aspnetcoretag-assistant": {
"type": "stdio",
"command": "dnx",
"args": ["Telerik.ASPNETCoreTag.MCP"]
}
}
}
Usage
By default, MCP clients do not call MCP tools in a deterministic way, unless you explicitly reference the MCP tool in your prompt. To use the Telerik MCP Server:
- Start your prompt with one of the following:
#and the MCP server name that you used inmcp.json(for example,#telerik-aspnetcoretag-assistant)#and the name of the Telerik ASP.NET CoreTagHelpers MCP tool (#telerik-aspnetcoretag-assistant)
- Confirm that the Telerik MCP server is used. Look for a statement in the output, which is similar to:
Running telerik-aspnetcoretag-assistant(in VS Code)Calling MCP tool telerik-aspnetcoretag-assistant(in Cursor)
- Grant the Telerik tool permission to run for the current session, workspace, or always.
- 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.
Also check the general AI Coding Assistant Recommendations for more usage tips.
To increase the probability of the Telerik ASP.NET CoreTagHelpers MCP Server being used, or to call it without the need to type "#telerik-aspnetcoretag-assistant" explicitly, add custom instructions to your AI-powered tool. Here are examples for GitHub Copilot and Cursor.
| Product | Versions 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. |
This package has no dependencies.