opencode

Prerequisites

• A ScaleReach API key (get one here)

Setup

Add to opencode.json (project root, or your global opencode config):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "scalereach": {
      "type": "remote",
      "url": "https://mcp.scalereach.ai/mcp/sr_live_YOUR_KEY_HERE",
      "enabled": true
    }
  }
}

Restart opencode to load the server.

Try it

• "Clip this YouTube video: [url]"
• "What videos do I have?"

See all available commands and caption styles.

What you can do from opencode

Once opencode is connected, you work in plain language and it calls ScaleReach for you. Clipping requests cover submitting a YouTube link, checking processing status, listing the clips that were generated, getting a download link for a clip, reprocessing a video with different settings, and deleting a video together with its clips. Scheduling requests cover listing your connected social accounts, scheduling a post for later, posting immediately, editing a pending post's caption, rescheduling it, and cancelling it.

opencode will ask for the same choices as any other client: genre, aspect ratio (9:16, 16:9 or 1:1), clip length, caption style and any custom focus. A 30-minute video usually takes 3 to 5 minutes to process, so ask opencode to check the status rather than expecting clips at once. Download links returned for clips are signed and last one hour, so ask for a new link if one has expired. See all available commands and caption styles for the full list.

Keep your API key private

The key is part of the URL you pasted into opencode, so anyone who sees the URL can use your workspace and spend your processing minutes. Do not paste the URL into public chats, screenshots, issues or commits. A key is limited to the workspace it was created in. If a key leaks, open Workspace Settings → API Keys in the dashboard, delete it, and create a new one; then update the URL in opencode. See Authentication for how keys work.

Troubleshooting

• opencode: Restart opencode after editing opencode.json. Older versions expect servers under mcpServers instead of mcp, so check opencode --version if the server never appears. Because opencode.json often lives in the repository root, keep your key in the global config for shared projects.
• The server connects but every call fails with 401: the key is wrong, expired or was deleted. A valid key starts with sr_live_ followed by 48 hex characters, and the URL must be exactly https://mcp.scalereach.ai/mcp/ followed by the key with no spaces or line breaks.
• A call fails with 402: the workspace has run out of processing minutes. Add minutes or change plan in the dashboard.
• Clips are not ready yet: the video is still processing. Ask opencode for the status again in a minute or two.
• Scheduling fails: connect at least one social account first, from Social → Connect Account in the dashboard.