MaxMSP MCP Server

What tiianhk/MaxMSP-MCP-Server MCP server does

The tiianhk/MaxMSP-MCP-Server MCP server lets an LLM work with Max patches through the Model Context Protocol. Its documented use cases include explaining an existing patch, generating Max objects, modifying a patch, debugging object usage, and checking whether its own changes are correct.

The project is aimed at Max/MSP/Jitter users building music and multimedia systems. The examples show an agent explaining a patch and creating an FM synthesizer. The agent can use official documentation for individual Max objects, as well as information about objects in the current patch and open subpatch windows.

How it works

The Python portion provides the MCP server and communicates with a Max patch. The repository includes a demonstration patch at MaxMSP_Agent/demo.maxpat. In that patch, the first tab contains messages for checking npm and installing JavaScript dependencies. The second tab provides the agent interface. A script start message begins communication with Python, after which the user can interact with the LLM interface.

The MCP client hosts the LLM and connects to the local server configuration. The installation instructions document setup for Claude and Cursor. Other MCP clients require adding their configuration path to install.py before using that script with the client name.

Setup and configuration

The tiianhk/MaxMSP-MCP-Server MCP server requires Python 3.8 or later, the uv package manager, and Max 9 or later. The Max version requirement is tied to scripts that use the JavaScript V8 engine; compatibility with Max 8 and earlier is not reported as tested.

The documented setup sequence is:

1. Install uv for the host operating system.
2. Clone the repository and change into its directory.
3. Create a virtual environment with uv venv.
4. Activate the environment and install dependencies from requirements.txt with uv pip install -r requirements.txt.
5. Run python install.py --client claude or python install.py --client cursor to connect one of the documented clients.

After opening or copying the demo patch, verify npm with the script npm version message, install the patch dependencies using script npm install, and start the Python connection with script start.

Tools and capabilities

The tiianhk/MaxMSP-MCP-Server MCP server supports these documented workflows:

• Explain the structure or behavior of a Max patch.
• Retrieve and explain information about Max objects.
• Use objects from the current patch and subpatch windows as context.
• Generate Max objects, including those needed for an FM synthesizer example.
• Modify objects in an existing patch.
• Debug and verify actions taken while working on a patch.

The material does not provide a named inventory of individual MCP tool functions, so capabilities are described at the workflow level rather than as specific tool names.

Limitations and notes

Max 9 or newer is required according to the project instructions. The repository states that Max 8 and earlier versions have not been tested. The implementation is third-party software and is not made by Cycling '74.

The README documents direct client setup for Claude and Cursor. Supporting another MCP client requires manually adding that client’s configuration path in install.py. The LLM provider, model, and any separate credentials are not specified in the supplied material. An extended version is maintained in a separate repository, but that is not the project described here.