RR MCP Server for .NET Analysis

What is RR MCP Server for .NET Analysis?

A generic MCP server for extracting .NET interface, OpenAPI, and data (models/entities/enums) information from any .NET solution using PowerShell scripts. It provides AI with large project structure and abstraction without exposing the contents.

How to use RR MCP Server for .NET Analysis?

Clone and build the project, then configure your MCP client with a stdio entry pointing to dotnet run --project <path>/RR.MCP.csproj. AI agents call the GetInterfaces and GetData tools, passing the .sln file path as the solutionFile parameter.

Key features of RR MCP Server for .NET Analysis

• Extracts Models, Entities, Enums, and Interfaces
• Gives AI full project structure/context
• Ready-to-use with Cursor, Copilot, Claude
• Fast with caching, clean output
• Auto-discovers scripts, supports relative/absolute paths
• Cross-platform, requires PowerShell 7+

Use cases of RR MCP Server for .NET Analysis

• AI agents analyze .NET solution without exposing code
• Extract interfaces and methods for documentation or refactoring
• Get data models and enums for code generation
• Integrate with any MCP-compatible AI IDE like Cursor

FAQ from RR MCP Server for .NET Analysis

What dependencies are required?

.NET 9.0 SDK or later, and PowerShell 7.0+ (pwsh must be set in PATH).

How does caching work?

Scripts cache per-project with hash-based approach. The first run on large projects may be slow; you can manually run the scripts to pre-warm the cache.

Where are logs and errors stored?

C# errors are logged to mcp_errors.log. PowerShell script activity and errors are logged to mcp_debug.log (interfaces) and mcp_data_debug.log (data) next to the scripts.

Is this server specific to a particular AI IDE?

No. It is fully generic and works with any MCP-compatible tool via stdio transport. Tools are auto-discovered and described via OpenAPI.

Can I customize which code constructs are extracted?

Yes. Edit the PowerShell scripts GetInterfacesPwsh.ps1 or GetDataPwsh.ps1, or add new [McpServerTool] methods in the C# tool files.