sonic-pi-mcp
by WEEZZ-admin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SONIC_PI_HOME | No | Custom Sonic Pi user-home root for logs and configuration. Optional. | |
| SONIC_PI_ROOT | Yes | Path to the Sonic Pi root directory, required for the server to locate daemon.rb and other resources. | |
| SONIC_PI_MCP_RUNTIME_DIR | No | Writable directory for temporary run_file buffers. Defaults to platform-specific cache directory (e.g., ~/.cache/sonic-pi-mcp). | |
| SONIC_PI_MCP_STARTUP_TIMEOUT | No | Timeout in seconds for Sonic Pi startup. Default: 60. | |
| SONIC_PI_MCP_EVENT_BUFFER_SIZE | No | Maximum number of events stored in the event buffer. Default: 5000. | |
| SONIC_PI_MCP_DEFAULT_COLLECT_MS | No | Default collection time in milliseconds for tool calls. Default: 1500. | |
| SONIC_PI_MCP_KEEPALIVE_INTERVAL | No | Interval in seconds for keep-alive messages. Default: 4. |
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
- 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/WEEZZ-admin/sonic-pi-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server