F
licenseA
qualityD
maintenanceEnables natural language control of Pure Data patches through Claude AI, allowing dynamic creation, modification, and DSP control via the Model Context Protocol.
11
22
-
PureData-MCP
Related Servers
Alternatives to PureData-MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables agentic interaction with vanilla Pure Data by providing tools for live patch creation, inspection, and manipulation via an MCP server that synchronizes with a Pd bridge patch.5-
- AlicenseNot gradedqualityFmaintenanceEnables LLMs to directly understand and generate Max patches via the Model Context Protocol.268MIT
- AlicenseAqualityDmaintenanceEnables AI-powered music composition and synthesis by generating Pure Data patches, VCV Rack modules, and MIDI controller mappings through natural language.1010 npm4MIT
- AlicenseAqualityBmaintenanceEnables LLMs to directly control, introspect, and build TouchDesigner networks in real-time through a Model Context Protocol server.25MIT
- AlicenseBqualityAmaintenanceA Model Context Protocol server that enables AI agents to control and operate TouchDesigner projects through creation, modification, and querying of nodes and project structures.14486 npm521MIT
TDQS
B3.2/5.0
Scored across 21 tools
Disambiguation4/5
Most tools target distinct actions (create, attach, stop, status), but pd_set_params and pd_send_control overlap in sending control messages, and the three start-related tools (pd_start_demo, pd_start_live_session, pd_open_patch) could be confused. Descriptions help disambiguate, but a few boundaries remain fuzzy.
Naming Consistency4/5
The naming pattern is largely pd_verb_noun, with a consistent pd_live_ prefix for canvas editing operations. However, a few tools like pd_status and pd_live_graph use nouns instead of verbs, breaking the otherwise predictable convention.
Tool Count3/5
With 21 tools, this sits in the heavy range (16-25) for a well-scoped MCP server. The breadth of Pure Data lifecycle and live-editing operations justifies many tools, but some could be consolidated (e.g., pd_start_demo and pd_start_live_session overlap).
Completeness4/5
The tool surface covers the full patch lifecycle (create, open, launch, preview, save, stop) plus detailed live canvas editing and parameter control. Minor gaps include no explicit DSP toggle and limited audio device configuration, but core workflows are well supported.
Maintenance
ActivityInactive
ResponsivenessNo issues