Skillget

mcp-binlog-tool

mcp
Guvenlik Denetimi
Uyari
Health Uyari
  • No license — Repository has no license file
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 16 GitHub stars
Code Gecti
  • Code scan — Scanned 5 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This is a Model Context Protocol (MCP) server that allows AI models to analyze and query MSBuild binary logs. It exposes tools for searching build diagnostics, measuring target execution times, and inspecting source files embedded within those logs.

Security Assessment
Overall Risk: Low. The server operates entirely via standard input/output (stdio) and processes local binary log files. It does not request dangerous system permissions. The automated code scan reviewed five files and found no dangerous patterns, hardcoded secrets, or malicious code. Because the tool reads local `.binlog` files, it will naturally access whatever build data and file contents the user provides to it, but it does not independently make external network requests or execute arbitrary shell commands.

Quality Assessment
This is an actively maintained, recently updated project. It features clear setup instructions, NuGet package integration, and a well-documented README. The main concern is the lack of a license file in the repository. Without an explicit license, the code is technically under exclusive copyright by default, which could restrict how organizations legally use or distribute it. However, its author is a recognized member of the developer community (baronfel), which adds an implicit layer of trust.

Verdict
Safe to use, though corporate users should note the missing software license before integrating it into commercial workflows.
SUMMARY

A Model Context Protocol server binary that exposes information inside an MSBuild Binary Log to LLMs to aid build analysis.

README.md

Binlog MCP Server

This is a simple demo of a Model Context Protocol Server (MCP) that exposes tools and prompts for analyzing MSBuild binlogs to any MCP server.

nuget.org link for this tool

Features

The server provides comprehensive tools for analyzing MSBuild binary logs, including:

  • Diagnostic Analysis: Extract warnings and errors from binlogs with filtering by severity, project, target, and task
  • Search Analysis: Powerful freetext search with MSBuild Structured Log Viewer query syntax support
  • Target Analysis: Identify expensive targets, search for specific targets across projects, and analyze target execution times
  • Project Analysis: Calculate project build times, find the most expensive projects, and analyze all targets in a project at once
  • Evaluation Analysis: List project evaluations, inspect global properties, and identify potential overbuilding issues
  • File Access: List and retrieve source files embedded in binary logs
  • Performance: Intelligent caching ensures fast queries even on large binlogs

See PACKAGE_README.md for detailed tool documentation.

Setup

Using the NuGet package

Claude

> claude mcp add binlog -- dnx baronfel.binlog.mcp -y
Added stdio MCP server binlog with command: dnx baronfel.binlog.mcp -y to local config

VSCode

If you have Claude configured already, you can tell VSCode to use the same settings by adding the following to your settings.json:

  "chat.mcp.discovery.enabled": true,

otherwise, you can configure the server directly:

{
  "servers": {
    "binlog-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["-y", "baronfel.binlog.mcp"]
    }
  }
}

Using local builds

To configure this:

  1. build the repo with dotnet build in the solution root directory
  2. configure Claude or VSCode to use the server
  3. launch your server app and have fun!

To locally debug, use npx to run the Model Context Protocol inspector::

npx @modelcontextprotocol/inspector ./artifacts/bin/binlog.mcp/debug/binlog.mcp.exe

Claude

{
  "mcpServers": {
    "msbuild": {
      "command": "<your repo root>\\artifacts\\bin\\binlog.mcp\\debug\\binlog.mcp.exe"
    }
  }
}

VSCode

If you have Claude configured already, you can tell VSCode to use the same settings by adding the following to your settings.json:

  "chat.mcp.discovery.enabled": true,

otherwise, you can configure the server directly:

{
  "servers": {
    "binlog-mcp": {
      "type": "stdio",
      "command": "<repo root>\\artifacts\\bin\\binlog.mcp\\debug\\binlog.mcp.exe",
      "args": []
    }
  }
}

Yorumlar (0)

Sonuc bulunamadi