cspy-debugger
Officialby iarsystems
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host interface for HTTP transport (default: 127.0.0.1). | 127.0.0.1 |
| MCP_PORT | No | Port for HTTP transport (default: 8000). | 8000 |
| THRIFT_FILE | No | Path to the Thrift IDL file; only needed when IDLs are outside this repo. | |
| MCP_TRANSPORT | No | MCP transport mode: stdio or streamable-http (default: stdio). | stdio |
| THRIFT_CSPYSERVER2 | No | Path to the CSpyServer2.exe executable (required for managed backend mode). | |
| THRIFT_INCLUDE_DIRS | No | Include directories for Thrift IDL; only needed when IDLs are outside this repo. | |
| THRIFT_REGISTRY_HOST | No | Hostname or IP of an already-running CSpyServer2/Service Registry (required for external backend mode). | |
| THRIFT_REGISTRY_PORT | No | Port of the Service Registry (required for external backend mode; can also be set via --registry-port). | |
| THRIFT_CSPYSERVER_ARGS | No | Arguments for the managed CSpyServer2 process (default: -standalone -sockets). | -standalone -sockets |
| THRIFT_REGISTRY_SERVICE | No | Name of the registry service to resolve (default: debugger). | debugger |
| THRIFT_CSPYSERVER_RESTART_ON_FAILURE | No | Set to '1' to restart a managed CSpyServer2 on failure. | 0 |
| THRIFT_EVENTHANDLER_CLIENT_TIMEOUT_MS | No | Timeout for the eventhandler listener in milliseconds (default: 3600000). | 3600000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/iarsystems/cspy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server