dump_package

Decompilation

Extracts all .dll and .exe files from a NuGet package folder structure into a single flat directory. This simplifies bulk analysis by collecting assemblies scattered across framework-specific subdirectories into one location where other mcilspy tools can operate on them directly.

Parameters

Parameter	Type	Required	Default	Description
assembly_path	string	Yes	—	Path to the assembly or NuGet package folder to extract from
output_dir	string	Yes	—	Directory to dump extracted assemblies into (created if needed)

Example

MCP JSON

{
  "tool": "dump_package",
  "arguments": {
    "assembly_path": "/path/to/packages/Newtonsoft.Json/13.0.3",
    "output_dir": "/tmp/newtonsoft-dump"
  }
}

Python

result = await client.call_tool("dump_package", {
    "assembly_path": "/path/to/packages/Newtonsoft.Json/13.0.3",
    "output_dir": "/tmp/newtonsoft-dump",
})

Response

Returns a summary with the output directory path and a list of all extracted assembly filenames. If no assemblies are found in the package structure, the response indicates that.

Usage tips

• After dumping, use list_types or decompile_assembly on any of the extracted assemblies.
• Useful for analyzing third-party NuGet dependencies when you need to understand their internals.
• The output directory is created automatically if it does not already exist.

Related tools

• list_types — explore the types in extracted assemblies
• decompile_assembly — decompile extracted assemblies
• get_assembly_info — check metadata of extracted assemblies