Telerik.CLI 1.2.0

Telerik CLI

Unified command-line interface for Telerik products and services. The CLI is published as a set of .NET global tools, all using the telerik command, each covering a distinct domain:

Global Options

Every command accepts a --json flag. When omitted, output is human-readable plain text. When present, the result is printed as indented JSON to stdout.

Every command also accepts a --verbose flag. When present, diagnostic messages are written to stderr, which is useful for troubleshooting.

Every command also accepts a --no-update-check flag. By default, the CLI checks for a newer version of itself after each command and prints a notice to stderr if one is available. Pass --no-update-check to suppress this check, which is useful in CI pipelines or latency-sensitive scripts.

Commands that require authentication (login, nuget config, license get-key) also accept a --no-browser flag for environments where the browser cannot complete the loopback OAuth redirect (e.g. firewall, antivirus, WSL, corporate proxy). When used, the command prints the authorization URL to the console, prompts you to open it in a browser and log in manually, then asks you to paste the full redirect URL from the address bar so the authorization code can be extracted and exchanged for an access token.

{
  "exitCode": 0,
  "success": true,
  "message": "Human-readable message",
  "data": { }
}

Session data and credentials are stored in an OS-specific state directory:

Commands

Setup

telerik setup

One-shot command that runs the full Telerik developer-machine setup in sequence:

1. login — authenticate with a Telerik account
2. nuget config — configure the Telerik NuGet package source
3. license get-key — download and store the Telerik license key
4. mcp config — register MCP server configuration for all detected IDEs

telerik setup [--scope user|project] [--nuget-path <path>] [--force] [--no-browser] [--interactive | --no-interactive] [--verbose] [--json] [--no-update-check]

• When --interactive is on (the default when stdin is a terminal), the user is prompted step-by-step through each stage.
• Pass --no-interactive to skip all prompts and run with explicit options or built-in defaults. This is the automatic default when stdin is redirected (e.g. in CI pipelines).

Authentication

telerik login

Authenticate with a Telerik account via browser-based OAuth. Persists the session locally so subsequent commands run without re-authenticating.

telerik login [--no-browser] [--verbose] [--json] [--no-update-check]

• If a valid session already exists, returns immediately without opening the browser.
• On success, stores access token, refresh token, email, and profile info in the state directory.
• Use --no-browser in environments where the browser cannot complete the loopback OAuth redirect (e.g. firewall, antivirus, WSL, corporate proxy). The command prints the authorization URL, prompts you to log in manually in a browser, then asks you to paste the full redirect URL from the address bar so the authorization code can be extracted and exchanged for an access token.

telerik logout

Clear the locally persisted login session.

telerik logout [--verbose] [--json] [--no-update-check]

telerik whoami

Display information about the currently authenticated user.

telerik whoami [--verbose] [--json] [--no-update-check]

NuGet

telerik nuget config

Add or update the Telerik NuGet package source (https://nuget.telerik.com/v3/index.json) in the user-level or a project-level NuGet.config.

telerik nuget config [--scope user|project] [--path <path>] [--api-key <key>] [--force] [--no-browser] [--verbose] [--json] [--no-update-check]

Licensing

telerik license get-key

Download and store the Telerik license key for the authenticated account.

telerik license get-key [--no-browser] [--verbose] [--json] [--no-update-check]

• Requires an active session (telerik login first), or pass --no-browser to authenticate inline.
• Stores the key file in the standard ProductLicenseKey location.
• Use --no-browser in environments where the browser cannot complete the loopback OAuth redirect (e.g. firewall, antivirus, WSL, corporate proxy). The command prints the authorization URL, prompts you to log in manually in a browser, then asks you to paste the full redirect URL from the address bar so the authorization code can be extracted and exchanged for an access token.

MCP

telerik mcp config <ide> <product>

Register a Telerik product's MCP server in the global MCP configuration file for a specific IDE. Upserts the server entry by name, preserving all other entries.

telerik mcp config [--ide <ide>] [<product>] [--verbose] [--json] [--no-update-check]

Passing all for either argument targets every known IDE or product respectively.

telerik mcp all

Convenience shorthand for mcp config all all — registers all known products into every detected IDE.

telerik mcp all [--verbose] [--json] [--no-update-check]

Supported products:

IDE configuration file locations:

Telemetry

The Telerik CLI collects telemetry to help improve CLI quality and reliability. You can opt out by setting the TELERIK_CLI_TELEMETRY_OPTOUT environment variable to 1 or true. When opted out, the CLI stops collecting telemetry.

Copyright 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.

Packaged distributions of Progress [insert product name] obtained from NuGet are made available pursuant to the Progress [insert product name] EULA at https://www.telerik.com/purchase/license-agreements, unless you have entered into a separate MSA with the licensor.