Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@trace32-mcp show me the current program counter value"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that wraps Lauterbach TRACE32's
public remote API (RCL) via the official lauterbach-trace32-rcl
(PyRCL) package. It lets an AI agent (e.g. GitHub Copilot agent mode) drive
TRACE32 PowerView for three MVP use cases:
Debugging — read/write memory, registers and variables; run control (go / break / step); breakpoints
Resource inspection — connection/run state, CPU, memory & register snapshots, PRACTICE function evaluation
Script execution & flash — run PRACTICE .cmm scripts, including SW target flash
Python 3.9+
TRACE32 PowerView already running with the remote API (RCL) enabled.
Add this to your config.t32 (blank line before/after each block):
RCL=NETTCP
PORT=20000Sanity-check it works before wiring up MCP:
t32rem localhost PRINT VERSION.SOFTWARE()Related MCP server: jlink-mcp
pip install -e .Variable | Default | Description |
|
| PowerView host |
|
| RCL port |
|
|
|
|
| UDP packet length (ignored for TCP) |
|
| Connection/request timeout (s) |
|
| Enables |
|
| Enables |
All read and debug-control tools are always available. Destructive operations are OFF by default and must be explicitly enabled:
T32_ALLOW_WRITE=true → memory/register writes, arbitrary command passthrough, script execution
T32_ALLOW_FLASH=true → flash programming (independent of T32_ALLOW_WRITE)
When a guard is closed, the tool returns an error explaining which flag to set — it never silently touches the target.
Workspace file .vscode/mcp.json is included. Adjust the env
values (host/port, and the guard flags when you intend to write/flash), then start
the server from the MCP view or the MCP: List Servers command. You can also run it
standalone:
python -m trace32_mcpTool | Guard | Purpose |
| — | Connection, run state, CPU, software build |
| — | Read N bytes → hex |
| — | Read register(s) |
| — | Read an HLL variable/symbol |
| — | Evaluate a PRACTICE function expression |
| — | Run control |
| — | Breakpoints |
|
| Write memory/register |
|
| Arbitrary TRACE32 command |
|
| Run a PRACTICE |
|
| Program target flash via a flash |
pytestUnit tests mock PyRCL, so no running TRACE32 is required. For end-to-end checks, the TRACE32 Instruction Set Simulator can stand in for real hardware.
Trace/CTS inspection, symbol/source browsing, multicore selection, call stack, peripheral register views, structured variable trees, multi-instance routing.
This server cannot be deployed
Live browser debugging for AI assistants — DOM, console, network via MCP.
Hunt zero-days by talking to binaries. 40+ tools. Hosted, OAuth + SSO, invite: hi@byteray.ai
Shared debugging memory for AI coding agents
