decompiler-mcp

DecompilerServer MCP

Use DecompilerServer as the primary source of truth for loaded .NET assemblies. Do not guess member IDs or fall back to shell scans after one failed symbol lookup; use the discovery and diagnostic tools first.

Default Workflow

1. Load or confirm context:
   • load_assembly with assemblyPath, or gameDir plus assemblyFile for Unity layouts.
   • list_contexts or status to confirm loaded and registered aliases and the current context. Passing contextAlias activates a registered alias on demand.
   • Use get_server_stats only when cache, index, or performance diagnostics matter.
2. Discover symbols:
   • Use search_symbols first for fragments or when unsure whether a name is a type or member.
   • Use resolve_member_id first for fully-qualified or XML-doc-like guesses such as Namespace.Type.Member, Namespace.Type:Member, or M:Namespace.Type.Member.
   • Use search_types when looking only for types.
   • Use search_members when looking only for methods, fields, properties, or events.
3. Inspect type surface:
   • Use list_members or get_members_of_type after resolving a type.
   • Prefer mode: "signatures" for orientation and mode: "full" only when extra metadata is needed.
4. Read code:
   • Use get_decompiled_source for complete focused source.
   • Use plan_chunking and get_source_slice for large types or methods.
5. Analyze relationships:
   • Use find_callers, find_callees, and find_usages for call/use questions.
   • Use find_base_types, find_derived_types, get_overrides, and get_implementations for inheritance questions.
   • Use get_il before proposing transpiler anchors; suggest_transpiler_targets should be treated as a real-IL hint list, not a substitute for reading IL.
6. Compare versions:
   • Use compare_contexts for structural alias-level overview.
   • Use compare_symbols for type/member drill-down.
   • Use compare_symbols with compareMode: "body" only for method bodies.