Pcm MCP Server

If you already use Pcm, the pcm mcp server is the piece that lets your assistant work with it directly. 1. Clone the repository git clone https://github.com/rand-tech/pcm 1. Add pcm to you mcp config example { "mcpServers": { "pcm": { "command": "uv", "args": [ "--directory", "path_to/pcm", "run", "server.py" ] } } } 1. Use.

What the server does

• repl (IDAPython)
• decompilation
• Engagement reports
• get_function_by_name(name): Get a function by its name
• get_function_by_address(address): Get a function by its address
• get_current_address(): Get the address currently selected by the user

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Analysis — IDA
• disassembly — decompilation
• Memory — Engagement reports

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of developer tooling 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. Pcm's toolset — Analysis, disassembly, Memory — is a fair guide to whether it matches your workflow. It is maintained by rand-tech; worth a glance at recent repository activity before you build anything load-bearing on it.

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.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.