mcp-mat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mat_healthcheckC | Validate MAT launcher and Java runtime availability. |
| mat_parse_reportC | Run a predefined MAT report headlessly and return generated artifacts. |
| mat_oql_queryC | Execute a single MAT OQL query and return result artifacts. |
| mat_index_statusB | Report whether MAT index artifacts already exist for a heap dump. |
| mat_run_command | Execute a named MAT analysis command headlessly and return result artifacts. Supports 56 built-in commands including: dominator_tree, path2gc, merge_shortest_paths, histogram, thread_overview, thread_details, collection_fill_ratio, gc_roots, find_strings, component_report, system_properties, and many more. Use mat_oql_query for OQL queries instead. |
| mat_oql_specA | Return MAT OQL parser-mode guidance, supported patterns, and known limitations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: environment validation, index checking, OQL query execution, OQL specification guidance, and report parsing. No overlaps or ambiguities exist.
All tool names follow a consistent 'mat_' prefix with snake_case, and each verb clearly indicates the action. The naming pattern is uniform and predictable.
With 5 tools covering essential MAT operations, the count is well-scoped. It is neither too sparse nor bloated for the server's purpose.
Core workflows (health, indexing, OQL queries, reports) are covered. A minor gap is the lack of tools to list or define custom reports, but the surface is otherwise complete.