Schema | py-spy MCP Server

py-spy MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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 }
`logging`	{}
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
record_profileA	Record a sampling profile of a Python process or command.
dump_stacksA	Dump the current Python call stacks of a process.
list_python_processesA	List running Python processes on this machine. Returns: A table of PID, memory usage, and command line.
analyze_profileA	Analyze an existing py-spy profile and return the hottest frames.
compare_profilesA	Compare two speedscope profiles and show percentage changes.
top_profileA	Run a live `py-spy top` view for a few seconds and return the summary. On Windows, `py-spy top` cannot be captured through a pipe, so this tool falls back to a short `record --format raw` sample and returns the hottest frames instead of raw top output.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`python_processes_resource`	Return a JSON list of currently running Python processes.

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LBurny/pyspy-mcp'

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