OpusClip MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-server-opus-video-clip -- npx -y @mindstone/mcp-server-opus-video-clip

{
  "mcpServers": {
    "mcp-server-opus-video-clip": {
      "args": [
        "-y",
        "@mindstone/mcp-server-opus-video-clip"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-server-opus-video-clip]
command = "npx"
args = ["-y", "@mindstone/mcp-server-opus-video-clip"]

{
  "mcpServers": {
    "mcp-server-opus-video-clip": {
      "args": [
        "-y",
        "@mindstone/mcp-server-opus-video-clip"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-server-opus-video-clip": {
      "args": [
        "-y",
        "@mindstone/mcp-server-opus-video-clip"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: OPUS_API_KEY (OpusClip API key (from https://app.opus.pro/settings/integration-tokens)), OPUS_API_TIMEOUT_MS (Outbound HTTP request timeout in milliseconds for general Opus API calls (max 1800000)), OPUS_UPLOAD_TIMEOUT_MS (Per-chunk HTTP request timeout in milliseconds for the GCS resumable upload step (max 1800000)), OPUS_BRIDGE_TIMEOUT_MS (HTTP request timeout in milliseconds for the optional host-app bridge (max 1800000)), MCP_WORKSPACE_PATH (Workspace directory the connector may read upload sources from and write downloaded clips to (defaults to the system temp directory)). The author declared them in the registry entry; get the values from the project itself.