Back to Signal Feed
CodeTracked since May 19, 2026

Add MCP-driven binlog failure analysis in dotnet-msbuild

This change registers a new `AITools.BinlogMcp` MCP server in the `dotnet-msbuild` plugin and rewires the `binlog-failure-analysis` skill to use MCP binlog tools as the primary flow, while keeping text-log replay as fallback when MCP is unavailable.

AITools.BinlogMcpdotnet-msbuildbinlog-failure-analysisMCP

What Happened

  • This change registers a new `AITools.BinlogMcp` MCP server in the `dotnet-msbuild` plugin and rewires the `binlog-failure-analysis` skill to use MCP binlog tools as the primary flow, while keeping text-log replay as fallback when MCP is unavailable.
  • This change registers a new `AITools.BinlogMcp` MCP server in the `dotnet-msbuild` plugin and rewires the `binlog-failure-analysis` skill to use MCP binlog tools as the primary flow, while keeping text-log replay as fallback when MCP is unavailable.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

The PR introduces a concrete integration change: plugin-level MCP server declaration plus skill-level execution rewiring to an MCP-first binlog analysis path. It changes the failure-analysis behavior from primarily text-log flow to structured MCP tool calls (for overview, errors, search, items, properties, imports, nuget), and updates evaluation guidance to reward MCP usage.

Why Track This

Why It Matters

Developers and operators debugging .NET build failures can now triage `binlog-failure-analysis` runs faster and with lower resource usage because the skill now defaults to MCP tools instead of relying only on replaying logs. In the provided local benchmark, token volume dropped 55%, tool-call count dropped 54%, and runtime dropped 80% (201.2s to 39.5s), with rubric quality improving from 3.6/5 to 4.0/5; continue watching MCP availability in runtime environments, behavior consistency after automatic dependency updates, and whether the unpinned prerelease MCP package source causes environment-specific breakage.

Impact

Developers and operators debugging .NET build failures can now triage `binlog-failure-analysis` runs faster and with lower resource usage because the skill now defaults to MCP tools instead of relying only on replaying logs. In the provided local benchmark, token volume dropped 55%, tool-call count dropped 54%, and runtime dropped 80% (201.2s to 39.5s), with rubric quality improving from 3.6/5 to 4.0/5; continue watching MCP availability in runtime environments, behavior consistency after automatic dependency updates, and whether the unpinned prerelease MCP package source causes environment-specific breakage.

What To Watch Next

  • Watch whether AITools.BinlogMcp becomes a repeated pattern.
  • Track follow-up changes around Model Context Protocol.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: mcp_server_availability_regression, mcp_server_prerelease_dependency_drift.
Open Topic TimelineOpen Technical EventOpen Original Sourcemcp_server_availability_regression / mcp_server_prerelease_dependency_drift / fallback_path_reliability_under_outage / mcp_tool_compatibility_with_existing_binlog_formats

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

dotnet/skills PR #673: dotnet-msbuild: register AITools.BinlogMcp and use it from binlog-failure-analysis

Adds AITools.BinlogMcp MCP server registration and updates `binlog-failure-analysis` to call MCP tools by default, improving analysis efficiency with evaluator results showing substantial reductions in tokens, tool calls, and runtime.