Get the FREE Ultimate OpenClaw Setup Guide โ†’

ILSpy

๐Ÿ”“ UNLEASH ILSpy'S POWER. Reverse-engineer DOTNET code at GOD SPEED. AI-assisted debugging that THINKS with you. Decompile ANYTHING. ๐Ÿš€

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio bivex-ilspy-mcp dotnet /path/to/ILSpy-Mcp.dll

How to use

ILSpy MCP Server exposes ILSpyโ€™s decompilation and analysis capabilities to MCP-compatible assistants. After you run the server, clients can send natural language prompts to decompile assemblies, inspect types and methods, explore type hierarchies, and search for specific members. Typical workflows include asking to decompile a given assembly, listing all types, or analyzing the structure of a namespace. The server translates these requests into ILSpy operations and returns readable results that can be further processed by the assistant or shown to the user. The environment is designed to be read-only for safety, with input validation and timeout support to ensure responsive interactions.

How to install

Prerequisites:

  • .NET 8.0 or higher installed on your system
  • ILSpy or ILSpy CLI available on the same machine
  • A MCP-compatible client (e.g., Cursor, Claude Desktop)

Installation steps:

  1. Clone the repository: git clone https://github.com/bivex/ILSpy-Mcp.git cd ILSpy-Mcp

  2. Build the project in Release configuration: dotnet build -c Release

  3. Run the server locally (example): dotnet build -c Release dotnet bin/Release/net8.0/ILSpy-Mcp.dll

  4. Configure your MCP client to point to the server:

    • Claude Desktop example (claude_desktop_config.json): { "mcpServers": { "ilspy-mcp": { "command": "dotnet", "args": ["/path/to/ILSpy-Mcp.dll"] } } }

    • Cursor example config: { "servers": { "ilspy-mcp": { "command": "dotnet", "args": ["/path/to/ILSpy-Mcp.dll"] } } }

Additional notes

Tips and common considerations:

  • Ensure ILSpy is installed and accessible from the PATH or provide the appropriate path for the ILSpy CLI usage if required by your build.
  • The server uses read-only operations; it validates assembly paths and supports operation timeouts to prevent hanging requests.
  • You can adjust configuration through environment variables or the clientโ€™s MCP settings depending on your deployment setup.
  • Provide full paths to assemblies when asking for decompilation or analysis to avoid ambiguity.
  • When deploying in production, consider containerizing the server and exposing only the MCP interface to trusted clients.

Related MCP Servers

Sponsor this space

Reach thousands of developers โ†—