
Mcp Mat
Let your agent analyze Java heap dumps headlessly through Eclipse MAT when you are debugging memory leaks or OOMs in production or staging.
Overview
mcp-mat is an Operate-phase MCP server that runs headless Eclipse MAT so agents can analyze Java heap dumps programmatically.
What is this MCP server?
- Headless Eclipse Memory Analyzer (MAT) exposed as an MCP server for agent-driven triage
- npm package mcp-mat v0.1.0 with stdio MCP transport
- Configurable MAT_HOME, JAVA_PATH, and MAT_XMX_MB (default 4096 MB heap for MAT)
- Suited to Java/Spring services where solo builders lack a dedicated JVM performance engineer
- Agent can orchestrate dump analysis steps instead of clicking through MAT GUI alone
- Server package version 0.1.0
- Default MAT_XMX_MB 4096 per environment variable schema
- stdio transport via npm identifier mcp-mat
Community signal: 19 GitHub stars.
What problem does it solve?
Java OOMs and leak hunts stall when you must manually operate MAT while the agent cannot see retained-object reports.
Who is it for?
Solo maintainers of Java backends who already capture hprof dumps and want MCP-driven MAT workflows in Claude Code or Cursor.
Skip if: Non-JVM stacks, teams without Eclipse MAT installed, or builders who only need lightweight JVM metrics without heap dumps.
What do I get? / Deliverables
After registration, your agent can invoke MAT-backed analysis on heap dumps using your local install and JVM settings.
- stdio MCP server wired to local MAT
- Agent-invokable headless heap analysis against your dumps
- Configurable MAT JVM heap via MAT_XMX_MB for large hprof files
Recommended MCP Servers
Journey fit
Canonical shelf is Operate → errors because heap dumps are diagnostic artifacts from failing or unstable JVM workloads. Errors subphase covers incident-driven debugging where MAT-style analysis replaces guesswork about retained objects.
How it compares
Specialized JVM heap-dump MCP bridge, not a generic log aggregator or application performance monitoring SaaS.
Common Questions / FAQ
Who is mcp-mat for?
Developers shipping Java services who use MCP agents and need Eclipse MAT analysis without living in the desktop UI for every incident.
When should I use mcp-mat?
Use it when you have a heap dump or recurring memory issues and want the agent to help interpret MAT output during operate-phase debugging.
How do I add mcp-mat to my agent?
Install the mcp-mat npm package, set MAT_HOME (and optionally JAVA_PATH and MAT_XMX_MB), add the stdio MCP server entry, and restart your client.