{
"mcpServers": {
"roslyn-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 3 days ago.
Will it work with my client?
Transport: stdio, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Roslyn Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Roslyn-backed MCP server for AI agents working with .NET solutions.
The project provides a sync-aware semantic layer over MSBuildWorkspace, so MCP clients can:
The server targets .NET 9 and supports both stdio and HTTP transports.
The current implementation is focused on read-only Roslyn tooling for agent workflows.
server_info
Returns basic server and runtime information.workspace_context
Resolves workspace context from an explicit solutionPath.diagnose
Checks environment readiness, MSBuild availability, and solution load health.load_solution
Loads a .sln, .slnx, or .csproj into a live Roslyn workspace.get_workspace_state
Returns the currently loaded workspace state and cached solution summaries.get_project_structure
Returns projects and, optionally, source documents for a loaded solution.get_document_outline
Returns a structural outline of a C# source file.get_file_overview
Returns a compact overview of a source file, including its main declarations.get_type_overview
Returns a compact overview of a resolved type.get_type_members
Returns members declared on the resolved type.search_symbols
Searches source declarations across the loaded solution.get_symbol_info
Resolves semantic symbol information at a file position.get_symbol_attributes
Returns attributes applied to the resolved symbol.go_to_definition
Returns source definition locations for the resolved symbol.get_method_signature
Returns the signature of a callable member at a file position.get_method_source
Returns the source body of a callable member at a file position.find_references
Finds source references for the resolved symbol.get_diagnostics
Returns compiler diagnostics for a solution or a specific file.validate_code
Returns a lightweight validity summary based on compiler diagnostics.find_implementations
Finds implementations of interfaces, abstract types, and virtual members.get_type_hierarchy
Returns base types, derived types, and interfaces for a resolved type.find_callers
Finds caller locations for callable symbols.get_outgoing_calls
Returns outgoing call edges for a callable member.analyze_method
Returns method-level data flow, control flow, signature, and outgoing call information.analyze_change_impact
Returns a best-effort impact summary for a symbol, including references and implementations.check_type_compatibility
Checks whether two resolved types are compatible.The server is designed for long-running agent sessions where files may change outside the Roslyn API.
It maintains a live workspace synchronization pipeline that:
Workspace.CurrentSolutionIn practice, this means tools such as find_references, analyze_method, and get_diagnostics can reflect edits made:
Build the solution:
dotnet build .\roslyn-mcp-server.sln -v minimal
Run the stdio host:
dotnet run --project .\src\RoslynMcpServer.Host.Stdio\RoslynMcpServer.Host.Stdio.csproj
Run the HTTP host:
dotnet run --project .\src\RoslynMcpServer.Host.Http\RoslynMcpServer.Host.Http.csproj -- --urls http://localhost:3001
The HTTP host exposes: