mcp.film / Review & Distribution / Frame.io MCP (community)
Frame.io MCP (community)
74 tools over the Frame.io V4 API — comments, shares, version stacks, uploads.
What it does
A local stdio MCP server for the Frame.io v4 API, built on FastMCP over Adobe's official Python SDK: browse workspaces and projects, upload and download footage, leave timecode-accurate review comments, create client share links, manage version stacks, apply custom metadata in bulk, and manage webhooks. Adobe now runs its own hosted server, listed as `frameio-official`, so this one matters mainly as a self-hosted, self-credentialed alternative.
Connect
Connection is set up through the vendor's flow — follow the official connect instructions.
Local install: uvx frameio-mcp serve (after a one-time uvx frameio-mcp login --client-id YOUR_ADOBE_SPA_CLIENT_ID)
FRAMEIO_CLIENT_ID — https://developer.adobe.com/console — add the Frame.io API and an OAuth Single Page App credential with redirect URI https://localhost:8723/callback; tokens land in ~/.frameio-mcp/tokens.json
Sample tools
list_projectslist_project_contentsupload_filecreate_commentcreate_sharecreate_version_stackset_file_metadatasearchField notes
The Claude Code plugin route is dead. github.com/bowlofarugula/frameio-plugins still 404s (rechecked 2026-09-30), so the old '/plugin marketplace add' command cannot work and claude_code is null. PyPI frameio-mcp 0.1.0 (uploaded 2026-06-04, not yanked) is still the only release. A uvx frameio-mcp --help and status run on 2026-08-11 installed clean. It needs Python 3.13+, and you must register your own Adobe OAuth SPA credential before it does anything. Its stated source repo has since been rewritten into a remote Cloudflare Workers server that you would have to deploy yourself. That repo still has 0 stars and has not been pushed since 2026-06-13, and its /authorize fails closed behind a redirect-URI allowlist, so there is no public endpoint. This is effectively unmaintained: treat it as a working snapshot, not a project. Use `frameio-official` instead unless you are on a Frame.io Legacy account. Adobe's own server went to public beta on 2026-10-07 with a documented hosted endpoint and Adobe ID OAuth, which removes the reason this entry existed. Legacy accounts are the one gap left: the official server does not support them. This server is built on the v4 API, so it has not been shown to work for them either.
Also in Review & Distribution
Adobe's hosted Frame.io MCP: review comments, shares, version stacks, uploads, and metadata.
Official Mux MCP: upload, manage, and analyze video via API or hosted remote server.
Social publishing and scheduling for YouTube and other channels, with clip jobs that cut long footage into shorts.
Official Vimeo remote MCP: library search, analytics, retention, and metadata editing.
Token-optimized YouTube Data API server for video, channel, and trend analytics.
Official Wistia remote MCP: upload, trim, caption, dub, publish, and read the analytics.
Used in
Local Edit Bay · Archive To Trailer · Turn an archive or dailies library into a trailer
Pairs well with
Official hosted Airtable MCP: query, create, and update production-tracking bases.
Official Cloudinary MCP for uploading, organizing, searching, and transforming media assets.
Dropbox's official remote MCP (beta) for dailies, footage folders, and file ops.