OpusClip MCP Server

What the code does

We read the source, 22 h ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

          fs.writeFileSync(outFd, pdfBuffer);

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const fullPath = path.join(stagingDir, filename);

    const child = spawn(process.execPath, [script], {

  if (isUnder(resolvedAbs, sshDir)) return { hit: true, reason: '~/.ssh/** is sensitive' };

  <script src="https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js"></script>

    const entries = fs.readdirSync(workspacePath, { withFileTypes: true });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 -e 'OPUS_API_KEY=<OPUS_API_KEY>' -- npx -y @mindstone/mcp-server-opus-video-clip

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

[mcp_servers.mcp-server-opus-video-clip]
command = "npx"
args = ["-y", "@mindstone/mcp-server-opus-video-clip"]
env = { OPUS_API_KEY = "<OPUS_API_KEY>" }

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

{
  "servers": {
    "mcp-server-opus-video-clip": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-opus-video-clip"
      ],
      "env": {
        "OPUS_API_KEY": "<OPUS_API_KEY>"
      }
    }
  }
}

Put your own value in place of <OPUS_API_KEY> (OpusClip API key (from https://app.opus.pro/settings/integration-tokens)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: 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)).