Maestro MCP 8ab55ab2

MCP开发工具

提供方 lewing

开发工具 未标注 Token 社区 / 第三方 Claude DesktopClaudeCursorVS Code

一个提供Maestro/BAR(构建资产注册表)数据缓存访问的MCP服务器及CLI工具,支持查询订阅、构建、通道和健康状态,适用于.NET构建基础设施的依赖流管理。

一句话选型结论

按资料字段整理

Maestro MCP 8ab55ab2 属于开发工具类 MCP 服务器,传输方式未标注,Token,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 20 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量20暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

依赖管理C#本地部署构建工具.NET基础设施缓存访问CLI工具

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 20 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 20 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Maestro MCP 8ab55ab2当前 20 未标注 未标注 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方lewing上游标注的维护方 lewing
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

19.0 KB
来自项目仓库与上游目录的原文,未做删改

maestro.mcp — MCP server & CLI for Maestro/BAR dependency flow data

An MCP server and standalone CLI tool that provides cached access to Maestro/BAR (Build Asset Registry) data for the .NET build infrastructure. Exposes 20 tools for querying subscriptions, builds, channels, and health status, plus triggering subscription updates and managing cache via the Model Context Protocol. Also works as a standalone CLI (mstro) for humans — same cached data, same authentication, no AI required.

Built with Squad — meet the squad.

Why mstro?

The Maestro/BAR API powers .NET's dependency flow infrastructure, but working with it directly is painful:

  • Subscription IDs are GUIDs — you need to query by repo/channel, not memorize UUIDs
  • Build staleness requires multi-step lookup — compare last-applied build vs latest available, then compute commit distance via GitHub
  • No cross-process caching — every darc invocation hits the API fresh, even for data that changes every 5–15 minutes
  • Codeflow status is opaque — backflow PRs, tracked PRs, and subscription history are scattered across multiple API endpoints

mstro wraps all of this in a single tool with smart caching (SQLite, shared across all MCP clients), automatic authentication (reuses darc Entra ID credentials), and enriched output (commit distance, health scoring, freshness checks). Whether you're an AI agent investigating a stale subscription or a human triaging build flow, you get the same fast, accurate answers.

Installation

Run with dnx (no install needed)

dnx (new in .NET 10) auto-downloads and runs NuGet tool packages — no install step required:```bash
dnx lewing.maestro.mcp


This is the recommended approach for MCP server configuration (see below). MCP stdio mode is the default.

### Install as Global Tool```bash
dotnet tool install -g lewing.maestro.mcp

For repo-local installation via a tool manifest:```bash
dotnet new tool-manifest # if .config/dotnet-tools.json doesn't exist
dotnet tool install --local lewing.maestro.mcp


### Install from Local Build```bash
dotnet pack src/MaestroTool
dotnet tool install -g --add-source src/MaestroTool/nupkg lewing.maestro.mcp

After installation, mstro is available globally.

Build from Source```bash

Prerequisites: .NET 10 SDK

git clone https://github.com/lewing/maestro.mcp.git
cd maestro.mcp
dotnet build


> **NuGet feed requirement:** The `Microsoft.DotNet.ProductConstructionService.Client` package is published to the
> dotnet-eng
> Azure Artifacts feed. The included `nuget.config` references this feed.

## Quick Start — CLI

`mstro` is a full CLI for humans. Every query uses the same cached API layer as the MCP server.```bash
# List subscriptions for a repo
mstro subscriptions --source-repository https://github.com/dotnet/runtime

# Get a specific subscription by ID
mstro subscription <guid>

# Check subscription health for a target repo (includes commit distance)
mstro subscription-health https://github.com/dotnet/sdk --include-commit-details

# Get the latest build for a repo on a channel
mstro latest-build https://github.com/dotnet/runtime --channel-name ".NET 10.0.1xx SDK"

# Get a specific build by ID
mstro build 302353

# List all channels
mstro channels

# List default channel mappings
mstro default-channels --repository https://github.com/dotnet/runtime

# Check build freshness via aka.ms
mstro build-freshness ".NET 10.0.1xx SDK"

# List active codeflow (backflow) PRs
mstro codeflow-prs --channel-name ".NET 10 Engineering"

# Get tracked PR for a subscription
mstro tracked-pr <guid>

# Get backflow status for a VMR build
mstro backflow-status 302627

# View subscription update history
mstro subscription-history <guid>

# Get build dependency graph
mstro build-graph 302353

# Get dependency flow graph for a channel
mstro flow-graph 1234 --days 14

# Get codeflow status (forward/backflow) for a repository
mstro codeflow-statuses https://github.com/dotnet/dotnet --branch main

# Trigger a subscription update (requires auth)
mstro trigger-subscription <guid> 302353

# Trigger all daily subscriptions (requires auth)
mstro trigger-daily-update

# Cache management
mstro cache status
mstro cache clear

All commands support --json for structured output and --no-cache to bypass the cache.

Interactive Detection

mstro automatically detects how it's launched:

Context Behavior
Terminal (no args) Shows --help with available commands
MCP host (stdin piped) Starts MCP server mode automatically
With subcommand Runs the specified CLI command

This means existing MCP configurations ("command": "mstro" with no args) continue to work unchanged — mstro detects the piped stdin and enters MCP server mode.

MCP Configuration

Add the following to your MCP client config. The --yes flag ensures dnx doesn't prompt for confirmation:```json
{
"servers": {
"maestro": {
"type": "stdio",
"command": "dotnet",
"args": ["dnx", "--yes", "lewing.maestro.mcp"]
}
}
}


> If you've installed `lewing.maestro.mcp` as a global tool, you can use `"command": "mstro"` with `"args": []` instead of `dnx`.

### With authentication```json
{
  "servers": {
    "maestro": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["dnx", "--yes", "lewing.maestro.mcp"],
      "env": {
        "MAESTRO_BAR_TOKEN": "your-token-here"
      }
    }
  }
}

HTTP server (alternative)```bash

dotnet run --project src/MaestroTool.Mcp


The HTTP server listens on **http://localhost:5000** by default.

### Config file locations

| Client | Config file | Top-level key |
|--------|------------|---------------|
| **GitHub Copilot CLI** | `~/.copilot/mcp.json` | `servers` |
| **VS Code / GitHub Copilot** | `.vscode/mcp.json` | `servers` |
| **Claude Desktop** (macOS) | `~/Library/Application Support/Claude/claude_desktop_config.json` | `mcpServers` |
| **Claude Desktop** (Windows) | `%APPDATA%\Claude\claude_desktop_config.json` | `mcpServers` |
| **Claude Code / Cursor** | `.cursor/mcp.json` | `mcpServers` |

## Authentication

The server implements a **3-tier authentication cascade**:

1. **Explicit PAT** — Set `MAESTRO_BAR_TOKEN` environment variable
2. **Cached Entra ID** — Reuses credentials from `darc authenticate` (`~/.darc/.auth-record-*`)
3. **Anonymous** — Read-only fallback (may be rate-limited)

**Recommended**: Run `darc authenticate` once (from arcade-services) to cache credentials, then rely on automatic Entra ID authentication.

## Action Tools

The server includes **action tools** for triggering subscription updates. These are non-destructive operations — they trigger processing but don't delete or modify subscription configuration.

### Deduplication

Action tools include built-in deduplication with a 2-minute cooldown. If the same action is triggered again within the cooldown window, the server returns a notice instead of re-executing. This prevents duplicate triggers from LLM retries or multiple concurrent skills.

### Destructive Actions (future)

Future versions may include destructive actions (delete subscription, remove default channel, etc.). These will be **disabled by default** and require an explicit opt-in:```json
{
  "servers": {
    "maestro": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["dnx", "--yes", "lewing.maestro.mcp"],
      "env": {
        "MAESTRO_ENABLE_DESTRUCTIVE_ACTIONS": "true"
      }
    }
  }
}

Available Tools

The server registers 21 MCP tools for querying and triggering Maestro/BAR operations:

Tool Name Description Key Parameters
maestro_subscriptions List all subscriptions sourceRepository, targetRepository, channelName, targetBranch (all optional filters); noCache: bypass cache
maestro_subscription Get a subscription by GUID ID, with health diagnostic subscriptionId: UUID; noCache: bypass cache
maestro_latest_build Get the latest build for a repository, optionally filtered by channel name repository: repo URL; channelName (optional); noCache: bypass cache
maestro_build Get a build by its BAR build ID buildId: build ID; noCache: bypass cache
maestro_builds List builds, optionally filtered by repository, channel, commit, or build number repository, channelName, commit, buildNumber, count (all optional); noCache: bypass cache
maestro_channels List all channels noCache: bypass cache
maestro_channel Get a specific channel by ID or name channelId: channel ID (integer) or channel name (string); noCache: bypass cache
maestro_default_channels Get default channels for a repository repository: source repository URL; noCache: bypass cache
maestro_subscription_health Check subscription health for a target repository — detects stale subscriptions and surfaces the latest trigger outcome (Updated/Failure/HasConflict/UserError/…) inline targetRepository: repo URL; noCache, includeCommitDetails, validate, staleOnly, compact (optional bools); channelFilter, sourceRepoFilter (optional strings)
maestro_build_freshness Check build freshness for a channel via aka.ms redirect channel: channel short name (e.g. '10.0.1xx'); noCache: bypass cache
maestro_trigger_subscription Trigger a subscription — provide buildId directly, or sourceRepository + channelName to auto-resolve subscriptionId: UUID; buildId (optional); sourceRepository, channelName (optional, for auto-resolve); force (optional bool)
maestro_trigger_daily_update Trigger all daily-update subscriptions None
maestro_codeflow_prs List active codeflow (tracked) pull requests managed by Maestro channelName (optional); noCache: bypass cache
maestro_codeflow_pr Get the tracked PR for a specific subscription subscriptionId: UUID; noCache: bypass cache
maestro_backflow_status Get backflow status for a VMR build vmrBuildId: build ID; noCache: bypass cache
maestro_subscription_history Get update history for a subscription — shows timestamped actions and errors subscriptionId: UUID; noCache: bypass cache
maestro_subscription_outcomes List recent subscription trigger outcomes from PCS (Updated / NoUpdate / NotUpdatable / Failure / UserError / HasConflict / Rescheduled), one outcome per line with emoji, build ID, PR URL, and message subscriptionId: UUID (optional); buildId, outcomeType, after, before, count (all optional; ISO 8601 for dates, 1–100 for count); noCache: bypass cache
maestro_build_graph Get the full dependency graph for a build buildId: BAR build ID; noCache: bypass cache
maestro_flow_graph Get the dependency flow graph for a channel channelId: channel ID; days: lookback (default 3, max 30); includeArcade, includeBuildTimes, includeDisabledSubscriptions (optional bools); noCache: bypass cache
maestro_codeflow_statuses Get codeflow status (forward flow and backflow) for a repository and branch repositoryUrl: repo URL (default: VMR); branch: branch name (default: main); noCache: bypass cache
maestro_clear_cache Clear the shared SQLite cache None

Naming Convention

Tools follow a consistent naming pattern:```
maestro_{resource} # get one by ID (e.g. maestro_build)
maestro_{resources} # list (e.g. maestro_builds)
maestro_{resource}{aspect} # detail query (e.g. maestro_subscription_health)
maestro
{verb}_{resource} # action (e.g. maestro_trigger_subscription)


### Cache Bypass

All read tools accept an optional `noCache` boolean parameter. When set to `true`, the cached entry for that request is invalidated before fetching, guaranteeing a fresh API call. Use this after triggering actions or when investigating rapidly changing state.

The `maestro_clear_cache` tool provides a full cache reset — useful when doing bulk operations or debugging stale data.

### Codeflow Tracking

The `maestro_codeflow_prs`, `maestro_codeflow_pr`, `maestro_backflow_status`, and `maestro_subscription_history` tools expose the same PCS PullRequest APIs used by the VMR codeflow tools (see dotnet/dotnet#4952). These tools enable visibility into codeflow PRs, backflow status, and subscription update history without requiring direct VMR access.

### Response Timestamps

All read tool responses include a retrieval timestamp header indicating when the data was fetched and whether it came from cache or a fresh API call:```
_Retrieved: 2026-02-18 15:30:45Z (cached)_

Data Enrichment

Beyond the raw Maestro/PCS APIs, this MCP server provides several value-added enhancements to improve visibility and decision-making:

Subscription Health Scoring — Compares each subscription's last-applied build against the latest available build on its channel, calculating exact BuildsBehind count. For GitHub-hosted source repos, the GitHub Compare API computes precise commit distance. For Azure DevOps repos, AzDo commit APIs provide detailed commit histories with author, message, and date.

Build Freshness via aka.ms — Resolves aka.ms short links to their final blob storage destination, then inspects the Last-Modified HTTP header to determine when a channel was last updated — without downloading artifacts. Includes SSRF protection against internal network redirects.

Channel Name Resolution — All tools accepting channelName perform automatic case-insensitive lookup to resolve human-friendly names (e.g., ".NET 10.0.1xx SDK") to numeric channel IDs. Callers never need to look up IDs manually.

Backflow Status Aggregation — For a given VMR build, aggregates per-branch backflow status including commit distance and subscription details across all target repositories.

State Oscillation Detection — Detects stuck subscriptions by analyzing update history for alternating ApplyingUpdates ↔ MergingPullRequest state cycles (per arcade-services#6090). Runs automatically for stale subscriptions during health checks.

Source-Manifest Tracing — For subscriptions targeting dotnet/dotnet, reads src/source-manifest.json from the VMR to determine what commit the VMR actually consumed, cross-referencing against the subscription's last-applied build.

Tracked PR Diagnosis — For stale subscriptions with tracked codeflow PRs, checks the GitHub PR state (merged-but-not-cleared, closed-but-not-cleared, blocked-by-CI, or active) to explain why the subscription is stuck.

Flow Graph Visualization — Formats the dependency flow graph with build times, longest-path critical path indicators, and channel routing information for end-to-end dependency analysis.

Human-Readable Formatting — All tool responses use emoji status indicators (✅ Current, ⚠️ STALE, ⏳ Pending, 🔒 Auth Required), structured tables, and visual markers for quick scanning. Commit details include SHA, message, author, and date when available.

Architecture

The project is split into three layers:```
src/
├── MaestroTool/ # CLI tool + stdio MCP server (dotnet tool)
│ └── Program.cs
├── MaestroTool.Core/ # Shared library — Maestro API logic + MCP tool definitions
│ ├── MaestroMcpTools.cs # MCP tool definitions ([McpServerToolType])
│ ├── MaestroService.cs # Cached business logic
│ ├── CacheService.cs # SQLite-backed cross-process cache
│ ├── IMaestroApiClient.cs # API abstraction
│ └── MaestroApiClient.cs # PCS client wrapper with auth cascade
├── MaestroTool.Mcp/ # MCP HTTP server (ASP.NET Core)
│ └── Program.cs
└── MaestroTool.Tests/ # Unit tests (167 tests)


- **MaestroTool** — Dual-mode entry point: standalone CLI for humans and stdio MCP server for AI agents. Packaged as a dotnet tool. Default entry point for `dnx` / `dotnet tool` usage.
- **MaestroTool.Mcp** — HTTP MCP server for remote/shared deployments.
- **MaestroTool.Core** — All business logic, caching, API client, and MCP tool definitions. Shared by both hosts.

### Cross-Process Cache Architecture

Multiple `mstro` instances (e.g., VS Code, Copilot CLI, and Claude Desktop running simultaneously) share a single SQLite cache at `~/.mstro/cache.db`. This eliminates redundant PCS API calls across clients.```mermaid
graph TB
    subgraph "MCP Clients"
        VSCode["VS Code<br/>Copilot Extension"]
        CLI["GitHub<br/>Copilot CLI"]
        Claude["Claude<br/>Desktop"]
    end

    subgraph "mstro Instances (separate processes)"
        M1["mstro<br/>MaestroMcpTools<br/>↓<br/>MaestroService"]
        M2["mstro<br/>MaestroMcpTools<br/>↓<br/>MaestroService"]
        M3["mstro<br/>MaestroMcpTools<br/>↓<br/>MaestroService"]
    end

    subgraph "Shared State"
        DB[("~/.mstro/cache.db<br/>SQLite (WAL mode)<br/>─────────────<br/>cache table (data)<br/>actions table (dedup)")]
    end

    subgraph "External API"
        PCS["Maestro / PCS API<br/>maestro.dot.net"]
    end

    VSCode -- "stdio" --> M1
    CLI -- "stdio" --> M2
    Claude -- "stdio" --> M3

    M1 -- "read/write" --> DB
    M2 -- "read/write" --> DB
    M3 -- "read/write" --> DB

    M1 -. "on cache miss" .-> PCS
    M2 -. "on cache miss" .-> PCS
    M3 -. "on cache miss" .-> PCS

    style DB fill:#f9f,stroke:#333,stroke-width:2px
    style PCS fill:#bbf,stroke:#333

Key design decisions:
- WAL (Write-Ahead Logging) mode enables concurrent reads across processes without blocking
- Separate tables for data cache and action dedup — maestro_clear_cache only clears data, trigger cooldowns survive
- Per-key TTL expiration with periodic cleanup of expired rows
- 10,000 entry cap with auto-eviction when capacity is reached

Cache TTLs

The CacheService uses SQLite with WAL mode for cross-process cache sharing. All mstro instances share ~/.mstro/cache.db:

Data Type TTL Reason
Subscriptions (list) 5 minutes Subscriptions change infrequently
Latest builds (by channel/repo) 5 minutes Builds are published frequently
Channels (list) 15 minutes Channels are rarely added/removed
Build by ID 30 minutes Builds are immutable once published
Build freshness (derived) 10 minutes Computed; cached to avoid repeated API calls

TTLs are configurable in CacheService if stricter freshness is needed. Expired entries are automatically cleaned up periodically.

Testing

Run the test suite:bash dotnet test

The test suite includes:
- 167 unit tests covering CacheService, MaestroService, security hardening, and tool behavior.
- Framework: xUnit + NSubstitute for mocking.
- Coverage: cache hit/miss, TTL expiration, null handling, error scenarios, commit distance, SSRF validation, corruption recovery.

Tests are located in src/MaestroTool.Tests/.

License

MIT


Contributing

For questions or issues, please open an issue in the repository. When modifying the authentication logic or adding new tools, ensure all tests pass and update this README accordingly.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Maestro MCP 8ab55ab2 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Maestro MCP 8ab55ab2 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Maestro MCP 8ab55ab2 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Maestro MCP 8ab55ab2 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Maestro MCP 8ab55ab2 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Maestro MCP 8ab55ab2 能提供哪些能力?

资料显示约 20 个工具;能力标签包括 依赖管理、C#、Claude、构建工具。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。