Source-install MCP server that connects Claude to Max, Max/MSP, and Jitter patches so it can inspect patch objects, add and remove objects, connect and disconnect patch cords, set attributes, send messages, trigger bangs, and use bundled Max object documentation while building or explaining patches.
MaxMSP MCP Server can add and remove Max objects, connect and disconnect patch cords, set object attributes, change message text, set number boxes, and send messages or bangs to named objects., These actions can alter a patch, trigger audio or visual behavior, destabilize a live performance patch, or change saved creative work if used on an important project., The Max-side bridge starts a Socket.IO server inside Max with permissive CORS in the reviewed source, so keep it bound to trusted local workflows and avoid exposing it to untrusted networks., The installer writes MCP client configuration files, so review paths and generated config before running it on shared or managed machines., The setup installs Python and npm dependencies from the source project; review dependency manifests before installing or running the bridge.
Privacy notes
Patch object names, arguments, comments, selected objects, subpatch structure, and generated Max documentation context can be sent to the MCP client and model., Prompts and transcripts can reveal unreleased music, audiovisual systems, installation designs, performance patches, plugin ideas, or teaching material., Socket.IO traffic between the Python server and Max can carry patch structure and command payloads, so keep the bridge on trusted local interfaces., Back up patches and avoid exposing proprietary samples, cue logic, show-control data, or private project notes through the MCP session.
Author
Haokun Tian and Shuoyang Zheng
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 6 risk areas. Review closely: credentials & tokens, network access, third-party handling.
6 areas
SafetyGeneralMaxMSP MCP Server can add and remove Max objects, connect and disconnect patch cords, set object attributes, change message text, set number boxes, and send messages or bangs to named objects.
SafetyGeneralThese actions can alter a patch, trigger audio or visual behavior, destabilize a live performance patch, or change saved creative work if used on an important project.
SafetyNetwork accessThe Max-side bridge starts a Socket.IO server inside Max with permissive CORS in the reviewed source, so keep it bound to trusted local workflows and avoid exposing it to untrusted networks.
SafetyLocal filesThe installer writes MCP client configuration files, so review paths and generated config before running it on shared or managed machines.
SafetyExecution & processesThe setup installs Python and npm dependencies from the source project; review dependency manifests before installing or running the bridge.
PrivacyThird-party handlingPatch object names, arguments, comments, selected objects, subpatch structure, and generated Max documentation context can be sent to the MCP client and model.
PrivacyExecution & processesPrompts and transcripts can reveal unreleased music, audiovisual systems, installation designs, performance patches, plugin ideas, or teaching material.
PrivacyExecution & processesSocket.IO traffic between the Python server and Max can carry patch structure and command payloads, so keep the bridge on trusted local interfaces.
PrivacyCredentials & tokensBack up patches and avoid exposing proprietary samples, cue logic, show-control data, or private project notes through the MCP session.
Safety notes
MaxMSP MCP Server can add and remove Max objects, connect and disconnect patch cords, set object attributes, change message text, set number boxes, and send messages or bangs to named objects.
These actions can alter a patch, trigger audio or visual behavior, destabilize a live performance patch, or change saved creative work if used on an important project.
The Max-side bridge starts a Socket.IO server inside Max with permissive CORS in the reviewed source, so keep it bound to trusted local workflows and avoid exposing it to untrusted networks.
The installer writes MCP client configuration files, so review paths and generated config before running it on shared or managed machines.
The setup installs Python and npm dependencies from the source project; review dependency manifests before installing or running the bridge.
Privacy notes
Patch object names, arguments, comments, selected objects, subpatch structure, and generated Max documentation context can be sent to the MCP client and model.
Prompts and transcripts can reveal unreleased music, audiovisual systems, installation designs, performance patches, plugin ideas, or teaching material.
Socket.IO traffic between the Python server and Max can carry patch structure and command payloads, so keep the bridge on trusted local interfaces.
Back up patches and avoid exposing proprietary samples, cue logic, show-control data, or private project notes through the MCP session.
Prerequisites
Python 3.8 or newer, uv, and the Python MCP CLI available to the configured MCP client.
Max 9 or newer, according to the upstream README.
npm available inside Max for the bundled MaxMSP_Agent bridge dependencies.
A cloned copy of the source repository and the MaxMSP_Agent bridge installed in the patch you want Claude to inspect or edit.
A backup or disposable copy of the Max patch before allowing Claude to modify objects, patch cords, messages, or attributes.
MaxMSP MCP Server is a source-install Model Context Protocol server for Max,
Max/MSP, and Jitter patch workflows. It connects a Python MCP server to a
Socket.IO bridge running inside Max so Claude can inspect patch contents, explain
objects, create objects, remove objects, connect and disconnect objects, set
attributes, update message boxes, set number values, and send messages or bangs
to named objects.
The project includes a bundled Max bridge patch and JavaScript helpers, a Python
MCP server, generated Max object documentation, and an installer that can add the
server to supported MCP clients. It is a third-party implementation and is not
made by Cycling '74.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, Python server, installer, dependency manifests, Max-side JavaScript
bridge files, and license file for current setup requirements, tool behavior,
bridge behavior, dependencies, and licensing.
Features
Source-install Python MCP server using FastMCP and python-socketio.
Local Socket.IO bridge between the MCP server and a Max patch.
Tools to add and remove Max objects, connect and disconnect objects, set
attributes, set message text, set number values, and send messages or bangs.
Tools to inspect objects in the current patch, inspect selected objects, read
object attributes, and find an avoid-rectangle position for new objects.
Bundled MaxMSP_Agent demo patch and Max JavaScript bridge files.
Bundled Max object documentation data used to help Claude explain and generate
patch elements.
Installer support for Claude, Cursor, and VS Code style MCP configuration
files.
MIT license.
Installation
Clone the project and install its Python dependencies:
Open a copy of the patch in Max, install the MaxMSP_Agent dependencies as
documented upstream, start the bridge inside Max, and then connect Claude to the
MCP server.
Use Cases
Ask Claude to explain the objects, connections, and signal flow in an approved
Max patch.
Generate a simple synthesizer, effect, controller, or Jitter patch structure
from natural-language instructions.
Debug a patch by inspecting selected objects and their attributes.
Add comments, messages, number boxes, or patch objects while iterating on a
teaching sketch.
Prototype Max/MSP ideas with Claude while keeping a human in control of
listening, testing, and saving.
Use object documentation context to choose valid Max objects and arguments.
Safety and Privacy
MaxMSP MCP Server is write-capable creative tooling. Run it on copies or
versioned patches first, especially for performance rigs, installations, class
materials, or paid client work. Claude can request object creation, deletion,
connection changes, attribute updates, and message/bang dispatches that may
produce sound, visuals, CPU spikes, feedback, or patch instability.
The bridge runs through a local Socket.IO server inside Max and can carry patch
structure plus edit commands. Keep it on a trusted local machine, avoid exposing
it to networks you do not control, and stop the bridge when you are done.
Review Python and npm dependencies before installing them, and inspect any MCP
client config generated by the installer before committing or sharing files.
Patch object names, comments, arguments, selected objects, subpatch structure,
and documentation-assisted prompts can reveal creative or commercial project
details. Avoid sending unreleased compositions, show-control logic, proprietary
patches, or private notes to a model session unless that use is approved.
Duplicate Check
No MaxMSP MCP Server, Max/MSP MCP, Jitter MCP, or
tiianhk/MaxMSP-MCP-Server entry was found in content/mcp, content/agents,
content/guides, or content/skills. This entry is scoped to the third-party
source-install Max/MSP MCP server and does not duplicate general creative-coding
or audio-production resources.
Show that MaxMSP MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/maxmsp-mcp-server)
How it compares
MaxMSP MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Source-install MCP server that connects Claude to Max, Max/MSP, and Jitter patches so it can inspect patch objects, add and remove objects, connect and disconnect patch cords, set attributes, send messages, trigger bangs, and use bundled Max object documentation while building or explaining patches.
Source-install MCP server for controlling Ableton Live from Claude, including session inspection, track and clip creation, MIDI note editing, tempo and transport control, browser item loading, arrangement workflows, device parameters, automation, external plugins, audio imports, and optional ElevenLabs.
MCP server for controlling Adobe After Effects through a local Node bridge and ScriptUI panel for compositions, layers, keyframes, expressions, masks, and effects.
✓MaxMSP MCP Server can add and remove Max objects, connect and disconnect patch cords, set object attributes, change message text, set number boxes, and send messages or bangs to named objects.
These actions can alter a patch, trigger audio or visual behavior, destabilize a live performance patch, or change saved creative work if used on an important project.
The Max-side bridge starts a Socket.IO server inside Max with permissive CORS in the reviewed source, so keep it bound to trusted local workflows and avoid exposing it to untrusted networks.
The installer writes MCP client configuration files, so review paths and generated config before running it on shared or managed machines.
The setup installs Python and npm dependencies from the source project; review dependency manifests before installing or running the bridge.
✓Ableton MCP Extended can create, rename, delete, arm, mute, solo, pan, and adjust tracks; create clips; add and delete MIDI notes; set tempo; start and stop playback; fire and stop clips; and manipulate arrangement content.
Device and plugin tools can load instruments or effects, enable or disable devices, delete devices, navigate presets, and change normalized parameters that may affect volume, routing, feedback, CPU load, or project sound.
Automation, cue point, loop, view, browser, sample import, and arrangement controls can make broad session changes that should be reviewed before saving.
The Ableton Remote Script runs a local TCP socket server inside Live; keep it available only to trusted local clients and close Ableton or remove the control surface when finished.
Voice generation and audio import workflows can create new audio files and may incur third-party API costs or licensing restrictions.
✓After Effects MCP queues predefined commands to a local bridge directory and relies on an open After Effects ScriptUI panel to execute them.
The bridge can create compositions, text layers, shape layers, solid layers, cameras, null objects, masks, keyframes, expressions, effects, and layer property changes.
Layer duplication, layer deletion, expression changes, masks, timing edits, and batch property updates can materially alter an After Effects project.
The install script may copy files into Adobe application folders and may require elevated privileges on some systems.
Enabling After Effects scripting permissions can let scripts write files and access network resources, so keep the bridge limited to trusted projects.
Use only the predefined script list exposed by the MCP server; do not modify it to accept arbitrary scripts unless that risk is understood.
✓Limit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.
Privacy notes
✓Patch object names, arguments, comments, selected objects, subpatch structure, and generated Max documentation context can be sent to the MCP client and model.
Prompts and transcripts can reveal unreleased music, audiovisual systems, installation designs, performance patches, plugin ideas, or teaching material.
Socket.IO traffic between the Python server and Max can carry patch structure and command payloads, so keep the bridge on trusted local interfaces.
Back up patches and avoid exposing proprietary samples, cue logic, show-control data, or private project notes through the MCP session.
✓Live Set names, track names, clip names, MIDI notes, device names, plugin lists, browser paths, sample paths, cue points, arrangement details, and generated audio prompts can be sent to the MCP client and model.
Optional ElevenLabs use can send voice prompts, generated-speech requests, and account metadata to a third-party API.
Local logs, model transcripts, imported audio files, and configured output directories can reveal unreleased music, client work, sample libraries, voice concepts, or performance plans.
Keep API keys scoped and out of committed MCP config, screenshots, issue comments, and shared prompt transcripts.
✓Tool calls and results can expose composition names, project structure, layer names, layer properties, timing, expressions, effect names, masks, and local bridge file paths.
Project contents may include client work, unreleased media, brand assets, filenames, text layers, and animation details.
The command and result files in the local bridge directory can persist recent instructions and After Effects output.
MCP client logs and model context may retain prompts, layer names, generated expressions, and project metadata.
✓Design contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.
Prerequisites
Python 3.8 or newer, uv, and the Python MCP CLI available to the configured MCP client.
Max 9 or newer, according to the upstream README.
npm available inside Max for the bundled MaxMSP_Agent bridge dependencies.
A cloned copy of the source repository and the MaxMSP_Agent bridge installed in the patch you want Claude to inspect or edit.
Ableton Live 11 or newer.
Python 3.10 or newer and pip for the source-install MCP server.
Git for cloning the source repository.
The AbletonMCP Remote Script copied into Ableton Live's User Remote Scripts directory and selected as a control surface.
Adobe After Effects 2022 or newer.
Node.js, npm, and a local checkout of the repository.
Permission to install the ScriptUI panel into the After Effects ScriptUI Panels folder.
After Effects scripting preferences reviewed, including whether scripts may write files and access the network.
Canva account (Canva Pro subscription recommended for full API access and team features)
OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
HTTP transport support in MCP client (required for Canva MCP server)
Internet connection for accessing Canva API (https://api.canva.com endpoints)