spx-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPX_KEY | Yes | The SPX HTTP key for authentication (e.g., dev) | |
| SPX_BASE_URL | Yes | The base URL of the SPX server (e.g., http://localhost) |
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 |
|---|---|
| profile_urlB | Profile one web request by sending SPX cookies to the target URL. |
| list_reportsB | List SPX report metadata from the embedded web UI data endpoint. |
| get_report_metadataC | Get metadata JSON for one SPX report key. |
| analyze_reportC | Download, decompress if needed, parse, and aggregate one SPX full report. |
| get_hot_pathsD | Return only the hottest call paths for one SPX report. |
| get_function_profileC | Return aggregate, callers, callees, and hot paths for a function name substring. |
| get_raw_eventsA | Return a paginated debug slice of raw SPX events. This never returns the full report. |
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 7 tools
Each tool has a clearly distinct purpose: profile_url initiates profiling, list_reports lists metadata, get_report_metadata retrieves specific metadata, analyze_report aggregates full data, get_hot_paths extracts hot paths, get_function_profile provides function-level analysis, and get_raw_events returns raw events. There is no ambiguity between them.
All tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., profile_url, list_reports, get_hot_paths). The verbs are clear and the naming is predictable throughout.
With 7 tools, the server is well-scoped for a profiling/analysis domain. Each tool covers a necessary operation without bloat, and the count is ideal for an agent to manage.
The tool set covers the core workflow: starting a profile, listing reports, retrieving metadata, performing full analysis, and extracting specific insights. Minor gaps exist (e.g., no explicit tool to stop a profile or delete reports), but these are likely outside the server's intended scope, and the remaining tools form a cohesive surface.