mcp-dotnet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ILSPYCMD | No | Absolute path to the ilspycmd executable (if not on PATH) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-typesA | List declared types in a .NET assembly (classes, interfaces, structs, delegates, enums). Use this first to find candidates before calling decompile-type. Works on .dll, .exe, and .NET 6+ single-file deployments (the embedded core assembly is decompiled directly). |
| decompile-typeA | Decompile a single fully-qualified type into C# source. Pass the fully qualified name as printed by list-types (e.g. 'Acme.Bot.LicenseManager'). |
| decompile-assemblyA | Decompile the entire assembly into a folder of .cs files (a compilable project). Use this when you want to grep across the whole codebase. Returns the output directory and a flat list of generated files. Heavy - prefer list-types + decompile-type for targeted lookups. |
| search-sourceA | Decompile the assembly to a temporary directory then grep its C# source for a pattern. Returns the matching files with line snippets. The decompiled tree is preserved on disk for follow-up queries (path returned in 'outDir'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list-types for browsing, decompile-type for a single type, decompile-assembly for full project, and search-source for pattern matching. No functional overlap.
All tool names follow a consistent lowercase hyphenated verb_noun pattern (e.g., list-types, decompile-assembly), ensuring predictability.
With 4 tools, the server is well-scoped for its domain—covering browsing, targeted decompilation, full decompilation, and source search without unnecessary redundancy.
The set covers core decompilation workflows (list, decompile single, decompile all, search). A minor gap exists for decompiling specific members without the full type, but the overall surface is sufficient for typical use.