Alias package for re-mcp-ida — installs re-mcp-ida
If you already use Ida, the ida mcp server is the piece that lets your assistant work with it directly. Alias package for re-mcp-ida — installs re-mcp-ida.
Both backends share a common tool interface — core analysis tools use the same names, parameters, and response shapes — so LLM workflows are portable across backends. Each backend also has tools for platform-specific features (e.g. IDA: file region mapping, executable rebuilding, IDC evaluation, IDAPython scripting; Ghidra: Function ID analysis, data type archives).
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Database — open/close/save/list databases, file region mapping, metadataFunctions — list, query, decompile, disassemble, rename, prototypes, chunks, stack framesDecompiler — pseudocode variable renaming/retyping, decompiler comments, microcodeCtree — AST exploration and pattern matchingCross-References — xref queries, call graphs, xref creation/deletionSearch — string extraction, byte patterns, text in disassembly, immediate values, string-to-code references, string list rebuildingData — raw byte reading, hex dumps, segment listing, pointer tablesPatching — byte patching, instruction assembly, function/code creation, data loadingSegments — create, modify, and rebase segmentsDemangling — C++ symbol name demanglingAnalysis — auto-analysis, fixups, exception handlers, segment registersSignatures — FLIRT signatures/type libraries (IDA), Function ID/data type archives (Ghidra)Configuration is passed through the environment: IDADIR, GHIDRA_INSTALL_DIR. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on PyPI as re-mcp-ida, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ida's toolset — Database, Functions, Decompiler and 11 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Database | open/close/save/list databases, file region mapping, metadata |
| Functions | list, query, decompile, disassemble, rename, prototypes, chunks, stack frames |
| Decompiler | pseudocode variable renaming/retyping, decompiler comments, microcode |
| Ctree | AST exploration and pattern matching |
| Cross-References | xref queries, call graphs, xref creation/deletion |
| Search | string extraction, byte patterns, text in disassembly, immediate values, string-to-code references, string list rebuilding |
| Data | raw byte reading, hex dumps, segment listing, pointer tables |
| Patching | byte patching, instruction assembly, function/code creation, data loading |
| Segments | create, modify, and rebase segments |
| Demangling | C++ symbol name demangling |
| Analysis | auto-analysis, fixups, exception handlers, segment registers |
| Signatures | FLIRT signatures/type libraries (IDA), Function ID/data type archives (Ghidra) |
| Export | batch decompilation/disassembly, output file generation |
| Snapshots | take, list, and restore database snapshots |
{
"mcpServers": {
"ida": {
"command": "uvx",
"args": ["re-mcp-ida"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| IDADIR | Filesystem location the server is allowed to use. | Optional |
| GHIDRA_INSTALL_DIR | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.