Other · Local MCP server

openDAW MCP

262 MCP tools for agent-native control of openDAW, a browser-based DAW.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.AMEOBIUS/opendaw-mcp
Version
1.13.0
Status
Active
Category
other
Transport
stdio (local process)
Package
OCI image (Docker)
Published
2026-07-04
Updated
2026-07-04
Publisher
AMEOBIUS (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/AMEOBIUS) · how
Listed under
Browser automation MCP servers
Repository
github.com/AMEOBIUS/opendaw-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
OCI image (Docker)ghcr.io/ameobius/opendaw-mcp:1.13.0-stdioOPENDAW_HOST_DIR (required), OPENDAW_URL (required), OPENDAW_EXPORT_DIR, NODE_BIN_DIR

How to connect openDAW MCP

openDAW MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/ameobius/opendaw-mcp:1.13.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e OPENDAW_HOST_DIR -e OPENDAW_URL -e OPENDAW_EXPORT_DIR -e NODE_BIN_DIR ghcr.io/ameobius/opendaw-mcp:1.13.0. It reads these environment variables: OPENDAW_HOST_DIR (required), OPENDAW_URL (required), OPENDAW_EXPORT_DIR and NODE_BIN_DIR; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "opendaw-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "OPENDAW_HOST_DIR",
        "-e",
        "OPENDAW_URL",
        "-e",
        "OPENDAW_EXPORT_DIR",
        "-e",
        "NODE_BIN_DIR",
        "ghcr.io/ameobius/opendaw-mcp:1.13.0"
      ],
      "env": {
        "OPENDAW_HOST_DIR": "<value>",
        "OPENDAW_URL": "<value>",
        "OPENDAW_EXPORT_DIR": "<value>",
        "NODE_BIN_DIR": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Openclaw Output Vetter MCPVerify AI agent claims vs reality: inline grounding-check + swallowed-exception + transcript review.Local · stdioPyPI: openclaw-output-vetter-mcp
Openclaw Skill Vetter MCPVet third-party AI agent extensions + agent-config files (AGENTS.md,.cursor/rules, CLAUDE.md).Local · stdioPyPI: openclaw-skill-vetter-mcp
Openclaw Upgrade Orchestrator MCPAI runtime upgrade safety + provider-side regression detection (snapshot diff + fingerprint).Local · stdioPyPI: openclaw-upgrade-orchestrator-mcp
OpenCode MCP BridgeCoordinate and verify OpenCode workers over MCP Streamable HTTP.Remote · HTTPLive check: sign-in requiredopencode-mcp.manuotel.com
Opendota MCPDota 2 heroes, match details, and player stats from OpenDota. No key required.Local · stdionpm: opendota-mcp
OpenemisRead-only MCP server for OpenEMIS - free open-source school management system. 675 resources.Local · stdionpm: openemis-mcp
Openemis ProRead + write MCP server for OpenEMIS - free open-source school management system. 675 resources.Local · stdionpm: openemis-mcp-pro
Openevidence MCPUnofficial MCP server connecting OpenEvidence to AI agents via authenticated browser sessions.Local · stdionpm: openevidence-mcp