Frame.io V4 MCP
This MCP server lets you authenticate with Frame.io V4, discover and invoke its API operations, and upload local files.
Start and complete OAuth to obtain a local access token.
Verify OAuth connection via GET /v4/me.
Search all 97 OpenAPI operations by text, tag, or HTTP method.
Retrieve official parameters and referenced schemas for an operationId.
Invoke any published Frame.io V4 operation; DELETE requires confirm=true.
Upload a local file through presigned URLs and return its upload status.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Frame.io V4 MCP find all comments on file FILE_ID in account ACCOUNT_ID with timecodes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frame.io V4 MCP
Node.js stdio MCP server backed by Frame.io's official V4 OpenAPI document. It exposes all 97 operations through a searchable catalog and adds complete local multipart upload handling.
MCP tools
start_oauth— creates the Adobe Native App PKCE authorization URLcomplete_oauth— exchanges the returned callback code and saves the access token locallyverify_connection— verifies OAuth withGET /v4/mesearch_tools— searches by text, API tag, or HTTP methodget_tool_schema— returns official parameters and referenced schemas for anoperationIdinvoke_tool— invokes any published operation; DELETE requiresconfirm: trueupload_local_file— creates an upload, PUTs each prescribed chunk, and reads upload status
The catalog covers accounts, workspaces, projects, folders, files, version stacks, comments, shares, reviewers, permissions, metadata, search, collections, groups, custom actions, webhooks, users, and audit logs.
Related MCP server: SandBase MCP
Install and run
Requires Node.js 20 or newer.
npm install
cp .env.example .env
npm run install:oauth-handler
npm startKeep .env private. The server never writes or prints credentials.
Each user normally creates their own OAuth Native App credential and keeps its Client ID, Redirect URI, and generated tokens only in their local .env. A shared Client ID requires publishing and approval of a common Adobe application.
Adobe Developer Console and OAuth
Sign in to Adobe Developer Console with the Adobe ID used for Frame.io V4.
Create a Developer Console project. This is an API application, not a Frame.io content project.
Choose Add API, select Frame.io API, and select OAuth Native App for user authentication.
Put the provided Client ID and Redirect URI in
.envasADOBE_CLIENT_IDandADOBE_REDIRECT_URI. Do not create or store a client secret.On macOS, run
npm run install:oauth-handleronce. It registers the credential'sadobe+…://Redirect URI scheme and writes callbacks only to the ignored local.oauth-callbackfile.Restart the MCP host after editing
.env. Callstart_oauth, open itsauthorizationUrlyourself, and approve access.After the native redirect opens, call
complete_oauthwithout arguments. It validates the persisted PKCE state, exchanges the code, and saves the access token to the ignored local.envwithout returning the token in MCP output.Verify only after login:
node probe.mjs verify_connection '{}'Official references: Getting Started, Authentication, Upload, and OpenAPI.
Examples
Discover the exact API operation before calling it:
node probe.mjs search_tools '{"query":"comments"}'
node probe.mjs get_tool_schema '{"operation_id":"comments.index"}'Timecoded client comments use the documented query parameter:
{
"operation_id": "comments.index",
"path": { "account_id": "ACCOUNT_ID", "file_id": "FILE_ID" },
"query": { "timestamp_as_timecode": true, "include": "owner,replies" }
}Creating a review link uses shares.create; its response contains short_url. New cuts can be uploaded and combined with an earlier file using version_stacks.create. Approval must come from explicit API evidence such as the production's configured metadata or review decision; zero unresolved comments alone is not treated as approval.
Tests
npm testThe checked-in OpenAPI document was retrieved on 2026-09-11 and has SHA-256 e7487c89bfebadca4d67ee9e7a6c38c56318d3d83a41d52f266cb05d6681c825.
Available Tools
5 toolsget_tool_schemaB
Get official parameters and referenced schemas for one Frame.io V4 operation.
Inputs: operation_id (required).
invoke_toolC
Invoke one operation from the official Frame.io V4 OpenAPI catalog. DELETE requires confirm=true.
Inputs: operation_id (required), body, path, query, +1 more.
search_toolsC
Search all operations in the official Frame.io V4 OpenAPI catalog.
Inputs: tag, limit, query, method.
upload_local_fileC
Upload a local file through Frame.io V4 presigned URLs and return its upload status.
Inputs: file_path (required), folder_id (required), account_id (required), name.
verify_connectionA
Verify Frame.io V4 OAuth by calling GET /v4/me.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: verify_connection checks OAuth, search_tools discovers operations, get_tool_schema retrieves parameter details, invoke_tool executes an operation, and upload_local_file handles file uploads. No two tools overlap in a way that would cause misselection.
All tool names follow a consistent snake_case verb_noun pattern (e.g., verify_connection, search_tools, get_tool_schema, invoke_tool, upload_local_file). There is no mixing of conventions.
Five tools are well-scoped for a meta-gateway that wraps the entire Frame.io V4 OpenAPI catalog. Each tool earns its place, and the count avoids both bloat and thinness.
The server provides full access to the Frame.io V4 API through search_tools, get_tool_schema, and invoke_tool, plus a specialized upload tool and an OAuth check. No obvious gaps exist for its stated purpose as a dynamic API gateway.
Maintenance
Related MCP Connectors
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.
- CueFrameDeprecatedai.cueframe.api
Compose, edit and render video through CueFrame’s hosted x402 MCP endpoint: content-aware reframing, word-timed captions and motion graphics. Paid tool calls require an x402-capable client and wallet payment. For OAuth browser sign-in, use the CueFrame OAuth connector.
Generate AI images and videos, quote credit costs, manage media and track batch jobs with OAuth.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables supported AI clients to discover, inspect, and execute 2,000+ models and APIs, including free data APIs and paid LLM, image, video, and audio calls, with OAuth, pricing checks, and rollback.556,724 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to discover, inspect, and run 2,000+ AI models and data APIs—including LLMs, image, video, and audio generation—through a single authenticated local bridge with per-call pricing shown before execution. It also supports run status tracking, account balance checks, and rollback from one browser sign-in.556,724 npmMIT
- AlicenseBqualityBmaintenanceEnables AI assistants to work with cloud content storage through natural language, covering file and folder operations, uploads and downloads, search, collaborations, shared links, metadata templates, tasks, groups, and user management. Supports multiple authentication methods and STDIO, SSE, and HTTP transports.117MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to search and browse an Immich photo library by content or metadata, inspect EXIF/people/albums/tags, view images and contact sheets, analyze duplicates and activity, and export browser-ready files with manifests. With an optional write key, it also enables curation such as favorites, ratings, descriptions, tags, albums, people, uploads, and reprocessing.MIT