ReelScribe MCP server

ReelScribe MCP Server

An MCP (Model Context Protocol) server that connects AI assistants to ReelScribe — transcribe Instagram Reels, TikTok videos, and YouTube videos directly from Claude, Cursor, Windsurf, and other MCP-compatible clients.

Setup

Hosted connector (Cloudflare Workers)

The endpoint is https://reelscribe.app/api/mcp. Add it as a remote connector in Claude or as an MCP connection in ChatGPT developer mode, then sign in to your ReelScribe account and approve access. Directory publication is a separate review process.

Hosted transcription returns a requestId immediately. Use get_transcription with that ID to retrieve the transcript after processing; submitting a duplicate returns the existing transcript. Account administration is available on the website.

Deploying

includeRetention response on /admin/get-user-by-clerk-id.

1. Deploy the accompanying ReelScribe API OAuth change, including the Convex

reelscribe:mcp, with consent text explaining permission to read transcripts and credit balance, and submit transcriptions that spend credits. Enable CIMD client onboarding, require S256 PKCE, and set the default scopes to reelscribe:mcp. For expanded workflows register an optional separate reelscribe:manage scope, retained under its existing name for compatibility. Its consent text must explain only batch/channel submissions that spend credits. Default scopes are reelscribe:mcp reelscribe:manage; a single-video client may request only reelscribe:mcp. Existing connections must explicitly approve the extra transcription permission on reconnect. Keep opaque access tokens enabled. Allow the intended clients to request the custom scope; enable DCR only for clients needing it.

1. In the production Clerk instance, create and advertise the custom scope

If Wrangler lists multiple accounts, set CLOUDFLAREACCOUNTID to that account.

1. Authenticate Wrangler with permission to deploy Workers in the SIÁN account.

bun run worker:deploy.

1. Run bun run typecheck, bun test, bun run worker:build, then

challenge, and the complete sign-in and transcription flow in both clients.

1. Verify /health, the public OAuth metadata, an unauthenticated /mcp 401

The branded URL is forwarded by the ReelScribe website to the existing Cloudflare Worker with branded=1, which selects matching OAuth resource metadata. The original https://reelscribe-mcp.sian-agency.workers.dev/mcp endpoint and its OAuth discovery remain available for existing connections. The domain is managed outside Cloudflare, so a direct Worker custom subdomain would require DNS changes.

The Worker holds no shared user API key or Clerk secret. It forwards each caller's token to ReelScribe's API, which verifies it with Clerk and resolves only that token's user. The base OAuth scope permits transcript, credit and job reads and single-video submission. Batch/channel submissions require separately granted reelscribe:manage consent. Despite its legacy name, this scope grants only transcription submission. Even existing management grants cannot access downloads, deletion, analytics or settings.

Local stdio setup remains available below.

1. Get an API Key

Sign up at reelscribe.app (25 free credits) and generate an API key from your API settings.

2. Configure Your MCP Client

Add to your MCP client configuration:

Claude Desktop (~/Library/Application Support/Claude/claudedesktopconfig.json):

{
  "mcpServers": {
    "reelscribe": {
      "command": "npx",
      "args": ["-y", "reelscribe-mcp-server"],
      "env": {
        "REELSCRIBE_API_KEY": "rs_your_api_key_here"
      }
    }
  }
}

Claude Code (~/.claude.json or project .mcp.json):

Shortened. The full README is on GitHub.