Apex Log MCP Server
OfficialServer 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apexlog_list_slow_operationsA | Rank what an Apex debug log spent its time on by self-execution time, or on the heap it retains - code units, methods, queries, searches, DML, flows and workflows in one table, each row with its calls, durations, database counts and rows, so the caller can see what to optimize and why, beside the query optimizer's plan for the queries among them. |
| apexlog_get_summaryA | Get a high-level summary of an Apex debug log: how long the transaction ran, where the time went by debug log category and the level each was logged at, every governor limit it and each namespace consumed, whether the log is complete, and what ended the transaction if it failed. Best for a quick overview. |
| apexlog_list_limit_risksA | List the governor limits an Apex log transaction has nearly consumed - CPU time, heap, SOQL and SOSL queries, DML statements, and the rows each returned or wrote - worst first, with how much of each was used |
| apexlog_execute_anonymousA | Execute a snippet of anonymous Apex against an authenticated Salesforce org (via SF CLI). Saves the resulting debug log to a local file and returns a summary with the file path, which the analysis tools accept. Production orgs require per-call user confirmation or the --allow-production-orgs server flag. |
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 4 tools
apexlog_execute_anonymous is clearly distinct as the only execution tool, and the three analysis tools are separated by focus (governor limits vs. time/heap ranking vs. overall summary). There is some genuine overlap since get_summary also reports time-by-category and per-namespace governor limits, which can shadow the two specialized list tools, but the descriptions explicitly frame one as a quick overview and the others as ranked deep-dives.
All four tools share the consistent 'apexlog_' namespace prefix and follow a clean verb_noun pattern (list_limit_risks, list_slow_operations, get_summary, execute_anonymous). The convention is predictable and readable across the whole set.
Four tools is a lean but mostly well-scoped surface for a focused Apex log analysis server, with each tool earning its place. It sits slightly on the thin side since a single execution tool feeds three analysis tools.
The server covers execution plus three angles of analysis, but there is no tool to retrieve or list existing debug logs already on the org, and no way to search/compare logs or run direct queries. Agents who need a log they did not just generate via execute_anonymous have no path, which is a notable gap.