@map-audio/mfx-mcp-server

MCP stdio server for MFX by MAP Audio. It lets MCP-compatible clients work with MFX routing, effects, modulation, transport, and presets.

Install

Requires Node 21 or newer:

npm install -g @map-audio/mfx-mcp-server
mfx-mcp --version

Add the launcher to your MCP client:

{
  "mcpServers": {
    "mfx": {
      "type": "stdio",
      "command": "mfx-mcp"
    }
  }
}

If the client cannot find mfx-mcp, use the absolute path printed by which mfx-mcp on macOS or where mfx-mcp on Windows.

Connect MFX

1. Open MFX Settings → Experimental.
2. Turn on Beta Features, then Enable MCP Bridge. The bridge starts immediately.
3. Start or restart the MCP client.

MFX starts at the configured bridge port. If that port is already occupied by another MAP Audio plugin instance, it automatically uses the next available port and records the actual port in the local bridge registry. MFX therefore does not need a separate fixed port.

The launcher pins both live discovery and offline lookup to MFX. Running another MAP Audio plugin at the same time cannot silently redirect mfx-mcp away from MFX.

The exposed MCP surface is MFX-specific:

• inspect and replace the four-cell cable patch;
• read and set each cable's gain;
• inspect, assign, label, lock, and move the three Combo controls with the MFX window closed;
• enable, order, and configure cell effects;
• create modulation and parameter sequencing;
• control transport and supported standalone settings;
• load, save, import, export, and manage MFX presets.

Sampler, song-arrangement, video, AI-model, and hosted-instrument workflows are not advertised by the MFX server. Third-party hosted-FX slot control is not yet available over MCP.

Preset saving uses the shared preservation rules: unreadable source files stop the save, and named copies retain the variation bank.

Version 0.2.0 uses PAM MCP 1.24.0 and adds get_preset_load_status. After load_preset, poll its request ID on the same instance until succeeded before editing or saving. This requires an MFX build with the tracked native preset-loading bridge actions.

Development

cd packages/mfx-mcp-server
npm --prefix ../mcp-server run build
npm run build
npm run dev

The entrypoint selects the bundled MFX manifest, preset namespace, bridge product, and package version before loading the shared MAP Audio MCP implementation. The package has an independent release line and must not be published before the MFX product release is approved.