MSBuild
About
Enables AI interaction with MSBuild project files for specialized .NET development workflows, providing tools and prompts for analyzing and manipulating project structures.
Details
- Author
- baronfel
- Repository
- baronfel/mcp-binlog-tool
- GitHub stars
- 1
- Categories
- Productivity, Developer Tools, Design, File Management, AI, Frontend, Infrastructure, Project Management
Jump to
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.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MSBuildCommand (node, npx, python, etc.)dnxArguments-
Argument 1
-y -
Argument 2
baronfel.binlog.mcp
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
-
Argument 1
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"msbuild": {
"cwd": "",
"env": {},
"args": [
"-y",
"baronfel.binlog.mcp"
],
"shell": false,
"command": "dnx"
}
}
}Linux
{
"cwd": "",
"env": [],
"args": [
"-y",
"baronfel.binlog.mcp"
],
"shell": false,
"command": "dnx"
}Macos
{
"cwd": "",
"env": [],
"args": [
"-y",
"baronfel.binlog.mcp"
],
"shell": false,
"command": "dnx"
}Windows
{
"cwd": "",
"env": [],
"args": [
"/c",
"<your repo root>\\artifacts\\bin\\binlog.mcp\\debug\\binlog.mcp.exe"
],
"shell": false,
"command": "cmd"
}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.
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": []
}
}
}
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
