ReelMafia guide
ReelMafia MCP Server: Connect AI Apps to Your Account
The ReelMafia MCP server lets AI apps work with your own ReelMafia account through your normal sign-in — start reel jobs, check progress, browse and search your reels, and restyle captions.
Updated
What the MCP server is
ReelMafia exposes an MCP (Model Context Protocol) server so AI apps can act on your own ReelMafia account. Point a compatible client at https://mcp.reelmafia.co/mcp and it can start reel jobs, check progress, browse and search your reels, and restyle captions — all through the same ownership checks the web app applies.
The server uses stateless Streamable HTTP. It never receives your password: sign-in uses the normal ReelMafia flow, the app returns a short-lived grant to the server, and the server mints a short-lived cookie for the approved user.
What the tools can do
Six tools are available. None of them delete anything, and create_reels is capped per user per UTC day.
- create_reels — start a reel job from a YouTube or video URL.
- get_job_status — check the progress of a job.
- list_my_videos — list finished videos, reels, and jobs in progress.
- get_reel_details — return reasons, scores, captions, and download links for one job.
- search_reels — search your own reels by title, summary, what is on screen, and what is said (typo-tolerant), plus related reels; each hit says where it matched.
- restyle_captions — re-burn captions with a new style, colour, or language.
Connecting a client
Claude (claude.ai, Desktop, or mobile): add a custom connector with the URL https://mcp.reelmafia.co/mcp, then sign in to ReelMafia and allow the request.
Claude Code: run claude mcp add --transport http reelmafia https://mcp.reelmafia.co/mcp, then run /mcp and choose Authenticate.
Cursor: add the server URL https://mcp.reelmafia.co/mcp to ~/.cursor/mcp.json under mcpServers; Cursor opens the browser to log in.
Scripts and CI that cannot do a browser login can use a static MCP_KEYS bearer token: Authorization: Bearer <token>.
The URL is all any MCP client needs — discovery and client registration are automatic.
How sign-in and security work
When an AI app connects, the server sends the browser to the ReelMafia sign-in. You sign in (password or Google), see who is asking, and click Allow. The app returns a signed, two-minute grant to the server — no password ever reaches the server.
Access tokens are signed, last one hour, and are bound to the server. Refresh tokens are stored hashed, rotated on every use, and re-using an old one revokes the whole chain. Signing keys are derived from the app's JWT_SECRET with a separate label per purpose, so a token for one purpose is useless for another.
Each tool call acts as you by minting a five-minute auth-token cookie for your account and calling the app's API, so the app's own ownership checks apply.
Limits and defaults
create_reels is limited to 10 jobs per user per UTC day by default, and the server rate-limits requests (120 per minute by default). Access tokens cannot be revoked individually but expire within an hour; refresh tokens can be revoked. The server is stateless, so more replicas are easy to add, though the in-memory rate limiter is per process.