An MCP server that analyzes MSBuild project graphs, detects build issues, analyzes dependencies, and provides insights into .NET solution structure and configuration.
Strong tool naming (all verb-first, clear intent) and comprehensive parameter schemas with type definitions. Descriptions are detailed and actionable (avg 180 chars, well above 10-char minimum). All 9 tools have input schemas with proper JSON types. However, output schemas are not explicitly documented in the source code, only inferred from return type annotations. Error handling is present but lacks recovery guidance (e.g., 'if circular dependency detected, try splitting projects'). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) visible in the MCP registration, though attributes exist in C# code. Missing per-parameter validation rules in descriptions (e.g., 'maxProjects must be 1-500').
Analyzes the impact of removing or modifying a specific project. Returns all projects that directly or transitively depend on the target project — answering 'what breaks if I change this project?' Example: analyze_impact("C:\src\MyApp.sln", targetProject: "CoreLib")
Evaluates MSBuild properties for a single project file with full source tracking — shows which file defined each property, whether it was imported, its line number, and any previous overridden values. Also lists the complete import chain. Without specific property names, returns key build properties. Example: analyze_project_properties("C:\src\MyLib\MyLib.csproj") Example with filter: analyze_project_properties("...", properties: ["LangVersion", "Nullable"])
Checks NuGet package version consistency across all projects in a solution. Finds packages referenced with different versions in different projects. Detects Central Package Management (CPM) and VersionOverride usage. Example: check_package_versions("C:\src\MyApp.sln")
Diffs two build configurations (e.g. Debug vs Release) for a project. Shows property differences, conditional PackageReference items, and conditional ProjectReference items between the two configurations. Example: compare_configurations("C:\src\MyApp\MyApp.csproj") Example: compare_configurations("...", config1: "Debug", config2: "Release", platform: "x64")
Output schemas not documented in MCP tool definitions. Return types are inferred from C# code (BuildIssueAnalysis, ProjectGraphResult, etc.) but not exposed as JSON Schema in the tool registration. LLMs cannot predict response structure without explicit schema documentation.
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) present in C# attributes but not visible in MCP protocol registration. Agents cannot determine which tools are safe to retry or have side effects without explicit protocol-level hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Analyzes a solution or project for build issues: circular dependencies, target framework mismatches between referencing projects, orphan projects (libraries that nothing references), and platform mismatches. Example: detect_build_issues("C:\src\MyApp.sln")
Discovers .props and .targets files shared across multiple projects in a solution. Identifies Directory.Build.props, Directory.Build.targets, and Directory.Packages.props. Shows which projects import each shared file. Example: find_shared_imports("C:\src\MyApp.sln")
Returns the correct build order (topological sort) for a solution or project. Lightweight output — just project names in order, plus critical path length. Ideal for understanding 'what builds first?' and parallelism potential. Example: get_build_order("C:\src\MyApp.sln")
Builds the MSBuild project dependency graph from a .sln or .csproj entry point. Returns all projects with their dependency edges, target frameworks, build order (topological sort), graph depth, and construction metrics. Multi-targeting projects are deduplicated — outer/inner builds grouped by path. Detects circular dependencies. Example: get_project_graph("C:\src\MyApp.sln", configuration: "Release")
Lists all projects in a solution file — fast, no MSBuild evaluation. Returns project names, paths, file extensions, and whether each exists on disk. Use this for a quick overview before running heavier analysis tools. Example: list_projects("C:\src\MyApp.sln")
Parameter constraints not documented in descriptions. 'maxProjects' defaults to 200 but no min/max bounds stated. 'configuration' and 'platform' are optional but no guidance on defaults or valid values (e.g., 'Debug|Release', 'AnyCPU|x64|x86'). LLMs may pass invalid values.
Error handling lacks recovery guidance. Circular dependency detection returns raw exception messages (e.g., 'MSB4251') without actionable next steps. Should guide: 'Circular dependency detected. Try: (1) review project references, (2) split into separate solutions, (3) use ProjectReference Condition attribute.'
No pagination support for tools returning large result sets. 'get_project_graph' truncates at 200 projects but offers no cursor/offset to fetch remaining. 'find_shared_imports' and 'list_projects' may return unbounded lists for large solutions.