maestro-cli

Access Maestro/BAR subscription and build data from the CLI as JSON.

13|20|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/arcade-skills --skill maestro-cli-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-cli
Source: https://github.com/dotnet/arcade-skills/tree/main/plugins/dotnet-dnceng/skills/maestro-cli
Command: npx skills add https://github.com/dotnet/arcade-skills --skill maestro-cli-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Access Maestro/BAR data from the CLI without requiring a loaded MCP server.

Core Features & Use Cases

  • Discovery-based data access via mstro; retrieve subscription health, latest builds, and codeflow statuses in JSON.
  • Suitable for one-shot scripting, health checks, and quick investigations when MCP server is unavailable or when you want structured output for pipelines.
  • Use cases include validating subscription health, tracing build graphs, and triggering subscription updates with minimal context load.

Quick Start

Install the mstro CLI and run a sample command such as mstro latest-build https://github.com/dotnet/runtime --json to see structured results.

Frequently Asked Questions about maestro-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query Maestro subscription health without loading a local MCP server?▼

You can query Maestro subscription health directly from the CLI using mstro. It retrieves JSON output for health checks and one-shot automation without requiring a loaded MCP server.

What is the best way to script Maestro BAR data retrieval for pipelines?▼

The best way to script Maestro BAR data retrieval is using the mstro CLI with the --json flag. It provides structured output suitable for pipelines and quick investigations when MCP tools are unavailable.

Do I need an authentication token to trace codeflow statuses with the mstro CLI?▼

You do not strictly need an authentication token to trace codeflow statuses. The mstro CLI uses a three-tier authentication cascade including MAESTRO_BAR_TOKEN, cached credentials, and anonymous mode.

How does the mstro CLI handle authentication when querying latest builds?▼

When querying latest builds, the mstro CLI handles authentication through a three-tier cascade: checking MAESTRO_BAR_TOKEN, falling back to cached credentials, and finally using anonymous mode.

Can I use the mstro CLI to trigger subscription updates with minimal context?▼

Yes, you can use the mstro CLI to trigger subscription updates with minimal context load. It supports one-shot scripting and progressive discovery through --help and guide commands.

What are the limitations of using a CLI for Maestro data instead of an MCP server?▼

Using the mstro CLI instead of an MCP server is limited to one-shot automation, health checks, and codeflow tracing. It relies on progressive discovery via --help rather than maintaining a persistent loaded server connection.