MCP Server

Most browser automation work still happens through a UI a human drives. MCP MCP server moves it into the conversation instead. Headless Eclipse MAT MCP server for Java heap dump analysis.

The short version

Headless MCP server for Eclipse MAT using direct java -jar org.eclipse.equinox.launcher_*.jar execution.

• mat_healthcheck — Validate MAT launcher and Java runtime availability
• mat_parse_report — Run predefined MAT reports (leak suspects, system overview, etc.)
• mat_oql_query — Execute OQL queries and return inline results
• mat_run_command — Execute 56 built-in MAT analysis commands (histogram, dominator_tree, path2gc, thread_overview, etc.)
• mat_index_status — Check whether MAT index artifacts exist for a heap dump
• mat_oql_spec — Return OQL parser guidance and supported patterns

The tools it exposes

The server publishes 2 tools. What each one is for:

• Export — The Export tool exposed by this server
• Codex — The Codex tool exposed by this server

What it needs from you

Configuration is passed through the environment: MAT_HOME, JAVA_PATH. 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.

Getting it running

The server ships on npm as mcp-mat, 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.

How it compares

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Export, Codex — is a fair guide to whether it matches your workflow. It is maintained by codelipenghui; 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.

Things to watch

• 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.