dotnet-decompiler-mcp
Related Servers
Alternatives to dotnet-decompiler-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceILSpy for LLM coding agents. Reflection-based MCP server with 31+ tools to explore .NET assemblies, NuGet packages, types, members, attributes, and XML docs.8MIT
- AlicenseAqualityCmaintenanceMCP server for .NET assembly analysis. Vendor-neutral wrapper around AsmResolver and ILSpy for parsing and decompiling .NET assemblies.111MIT
- FlicenseBqualityBmaintenanceMCP server for searching, browsing, and analyzing decompiled Minecraft source code locally. Supports symbol lookup, text search, reference lookup, and lightweight RAG.11-
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that gives AI assistants Roslyn-powered browsing of any C# solution, letting them list types by folder or namespace, read XML documentation, and retrieve method signatures, locations and bodies. This keeps queries targeted so agents pull only the exact slice of source they need instead of reading whole files into context.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes an AI decompiler via an OpenAI-compatible API, enabling decompilation, explanation, and variable renaming of disassembly for binary analysis.MIT
- AlicenseNot gradedqualityFmaintenanceMCP server that allows LLMs to autonomously reverse engineer applications using Ghidra, exposing tools like decompilation, renaming, and listing methods.27Apache 2.0
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: environment checking, decompiling types, decompiling members, getting type summaries, listing namespaces, listing types, and searching symbols. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern: check_env, decompile_member, decompile_type, get_type_summary, list_namespaces, list_types, search_symbol. The pattern is uniform and predictable.
Seven tools is an ideal size for a decompiler MCP server, covering diagnostics, exploration, and decompilation without being overwhelming or insufficient.
The tools cover the core exploration and decompilation workflow (list namespaces, types, summary, decompile type/member, search). However, missing are options for decompilation settings (e.g., with/without comments, debug info), which would make it fully complete.