Pure Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PD_OSC_HOST | No | Host for OSC communication with Pure Data | 127.0.0.1 |
| PD_OSC_PORT | No | Port for OSC communication with Pure Data | 5000 |
| PD_FEEDBACK_PORT | No | Port for feedback from Pure Data | 5001 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_objectA | Create a new Pd object. |
| delete_objectA | Delete a Pd object. |
| connect_objectsA | Create a connection between two Pd objects. |
| disconnect_objectsB | Remove an existing connection between two Pd objects. |
| set_paramA | Modify a parameter of an existing Pd object. |
| get_paramB | Retrieve the current value of an object's parameter. |
| clear_workspaceA | Clear all objects from the Pd workspace subpatch and reset index tracking. |
| start_dspB | Enable DSP processing in Pure Data. |
| stop_dspA | Disable DSP processing in Pure Data. |
| save_patchB | Save the current Pd patch. |
| load_patchC | Load a Pd patch from a file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_oscillator_patch | Prompt to create a simple oscillator patch. This prompt guides the user through creating a basic oscillator patch in Pure Data using the available tools. Returns: Prompt text |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| pd://objects | |
| pd://port-info |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: object creation/deletion, connection management, parameter access, file operations, DSP control, and workspace clearing. There is no overlap or ambiguity among the tools.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_object, get_param, start_dsp). No mixed conventions or deviations are present.
With 11 tools covering object lifecycle, connections, parameters, file persistence, and DSP state, the count is well-scoped for a Pure Data server. Every tool serves a necessary function without redundancy.
The tool set covers core operations (CRUD for objects, connections, parameters, patch files, DSP) but lacks a tool to list all objects or send arbitrary messages. These minor gaps are acceptable for many use cases.