OpusClip

OpusClip runs locally from a Node.js package published to the npm registry: @mindstone/mcp-server-opus-video-clip version 0.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @mindstone/mcp-server-opus-video-clip@0.2.1. It reads these environment variables: OPUS_API_KEY (required, secret), OPUS_API_TIMEOUT_MS, OPUS_UPLOAD_TIMEOUT_MS, OPUS_BRIDGE_TIMEOUT_MS and MCP_WORKSPACE_PATH; 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": {
    "mcp-server-opus-video-clip": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-opus-video-clip@0.2.1"
      ],
      "env": {
        "OPUS_API_KEY": "<secret>",
        "OPUS_API_TIMEOUT_MS": "<value>",
        "OPUS_UPLOAD_TIMEOUT_MS": "<value>",
        "OPUS_BRIDGE_TIMEOUT_MS": "<value>",
        "MCP_WORKSPACE_PATH": "<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