ScaleReachScaleReach API
Connect Your Tools

Zapier

Call ScaleReach's tools from a Zap using MCP Client by Zapier.

Prerequisites

Setup

  1. In your Zap, add an action step and search for MCP Client by Zapier
  2. Choose the MCP Client action
  3. When prompted for a connection, click Connect a new account
  4. Server URL: https://mcp.scalereach.ai/mcp/sr_live_YOUR_KEY_HERE
  5. Transport: Streamable HTTP
  6. OAuth: No
  7. Leave Bearer Token empty - your key is already in the URL
  8. Click Yes, Continue

Zapier loads ScaleReach's tools (submit video, get status, get clips, schedule post, etc). Pick the one you want and map its inputs to data from earlier steps in your Zap.

The key-in-URL form above is the primary documented setup. If it fails, Zapier also supports a Bearer Token; use this fallback only if your ScaleReach endpoint accepts header authentication:

  • Server URL: https://mcp.scalereach.ai/mcp
  • OAuth: No
  • Bearer Token: sr_live_YOUR_KEY_HERE (without Bearer; Zapier adds it)

Try it

Example Zap: New row in Google Sheets → MCP Client (submit_youtube_video) → Slack notification

See all available commands and caption styles.

What you can do from Zapier

Once Zapier 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.

Zapier 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 Zapier 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 Zapier, 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 Zapier. See Authentication for how keys work.

Troubleshooting

  • Zapier: Reconnect the account in the MCP Client step with Connect a new account. If Zapier rejects the key-in-URL form, use the Bearer Token fallback shown above.
  • 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 Zapier 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.

On this page