New to Telerik UI for Blazor? Start a free 30-day trial

Telerik CLI

Updated on Mar 17, 2026

The Telerik CLI is a .NET tool that can help you set up your Telerik development environment, including:

Install or update your license key.
Set up the Telerik NuGet feed.
Install the Telerik Blazor MCP server.

Installation

The Telerik CLI NuGet package is hosted on nuget.org. To install the Telerik CLI .NET tool globally on your computer, run the following command in your preferred command shell:

Install Telerik CLI

dotnet tool install -g Telerik.CLI

Without the -g flag, .NET installs the tool in the current folder only.

To verify successful installation, run:

Confirm Telerik CLI installation

dotnet tool list -g

To update the Telerik CLI to the latest version, run:

Update Telerik CLI

dotnet tool update telerik.cli -g

To uninstall the Telerik CLI, run:

Uninstall Telerik CLI

dotnet tool uninstall -g Telerik.CLI

Usage

Each Telerik CLI command starts with the telerik tool name, followed by the respective command and options. First, log in the CLI to use the other commands effectively.

Help

To get help about the tool or a specific command, use the -h option:

Getting help in the Telerik CLI

telerik -h

telerik nuget -h

telerik nuget config -h

Most Telerik CLI commands rely on authentication. If you are not logged in the CLI before command execution, the web browser opens https://identity.telerik.com where you need to provide your Telerik account credentials. On successful authentication, the browser redirects to https://login.telerik.com and then to localhost. If this browser integration fails due to security or network settings, you can also authenticate manually. In this case, use the --manual option, which is available for the following Telerik CLI commands:

login
license get-key
nuget config

Using Telerik CLI commands with manual authentication

telerik login --manual

telerik license get-key --manual

In manual mode, the CLI outputs a link to https://identity.telerik.com for you to open in a browser. On successful authentication, the browser redirects to https://login.telerik.com. Copy this URL, paste it in the CLI, and press Enter.

The Telerik CLI can fall back to manual authentication even if the --manual option is not set. This happens if the automatic authentication takes longer than three minutes.

Command Output

Each Telerik CLI command has two output formats:

Human readable (default)
JSON—to use it, append the --json option

Telerik CLI output format comparison

telerik whoami
Logged in as john.doe@telerik.com.

telerik whoami --json
{
  "exitCode": 0,
  "message": "Logged in as john.doe@telerik.com.",
  "data": {
    "email": "john.doe@telerik.com",
    "firstName": "John",
    "lastName": "Doe"
  },
  "success": true
}

Log In

Most Telerik CLI commands are related to your Telerik identity. It's recommended to log in first, so that all the other commands work without the need for additional authentication:

telerik login

The login command opens https://identity.telerik.com in a browser window where you need to provide your Telerik account credentials. Then the browser makes of couple of redirects. If this process does not succeed, see Manual Authentication above.

The Telerik CLI stores a session token in:

Operating System	Path
Windows	`%AppData%\Telerik`
macOS / Linux	`~/.telerik`

The session token is valid for one month.

To see which Telerik user is logged in the CLI, use the whoami command:

telerik whoami

The CLI will output your Telerik user account email.

Log Out

To log out from the Telerik CLI, use the logout command.

telerik logout

Get License Key

To download or update your Telerik license key, use the license get-key command:

telerik license get-key

The license get-key command downloads your up-to-date Telerik license key and creates a telerik-license.txt file in your operating system user's folder.

Set Up NuGet Feed

To add the Telerik NuGet server to your package sources, use the nuget config command:

telerik nuget config

By default, the nuget config command updates your global NuGet.Config file. The newly added Telerik NuGet feed name is TelerikNuGetV3. The command generates a new API key that you can delete and revoke from the API Keys page in your Telerik account.

Telerik NuGet API keys expire in two years.

You can use the nuget config command with the following options:

--scope project and --path that points to the folder that contains the NuGet.Config file to modify.
--api-key to provide an existing Telerik NuGet API key inline, otherwise the CLI generates a new one.
--force to overwrite any existing Telerik credentials in the NuGet.Config file.

telerik nuget config --scope project --path . --force

Install MCP Server

To install the Telerik Blazor MCP server, use the mcp config command:

telerik mcp config

By default, the command creates or updates the global mcp.json configuration files of all supported IDEs with all available Telerik MCP servers.

IDE	Operating System	Configuration File Path
Visual Studio	Windows	`%USERPROFILE%\.mcp.json`
VS Code	Windows	`%APPDATA%\Code\User\mcp.json`
VS Code	macOS	`~/Library/Application Support/Code/User/mcp.json`
VS Code	Linux	`~/.config/Code/User/mcp.json`
Cursor	Windows	`%USERPROFILE%\.cursor\mcp.json`
Cursor	macOS, Linux	`~/.cursor/mcp.json`

You can also fine-tune the process with the following options:

Specify which Telerik products you are interested in, for example, just blazor.
--ide specifies your preferred IDE. The supported values are visualstudio, vscode, cursor, and all.

telerik mcp config blazor --ide visualstudio