Schema | spx-mcp-server

spx-mcp-server

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)

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/szepeviktor/spx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server