# Frame.io MCP

> Adobe's hosted Frame.io MCP: review comments, shares, version stacks, uploads, and metadata.

- **Category:** Review & Distribution
- **Vendor:** Adobe (Frame.io) (official)
- **Pricing:** freemium
- **Verified:** 2026-10-10

## What it does

Frame.io's official remote MCP server puts the review-and-approval layer of a production in front of an agent: search assets across workspaces, read and write review comments, build version stacks, upload media, edit metadata fields, and manage share links, reviewers, and project members. Adobe says it adds nothing the V4 API cannot already do. What it adds is the ability to chain those calls from a prompt. For a film pipeline, that means turning a round of client notes into a task list, or stacking the new cut on the old one and sending the share link, without anyone opening the browser.

## Connect

- Remote endpoint: `https://mcp.frame.io/v1/mcp`
- Claude Code: `claude mcp add --transport http frameio https://mcp.frame.io/v1/mcp`

**Auth:** oauth — OAuth through Adobe IMS — sign in with the Adobe ID linked to your Frame.io account

## Capabilities

[review-comments](https://mcp.film/capabilities/review-comments.md) · [share-links](https://mcp.film/capabilities/share-links.md) · [version-stacks](https://mcp.film/capabilities/version-stacks.md) · [asset-upload](https://mcp.film/capabilities/asset-upload.md) · [metadata](https://mcp.film/capabilities/metadata.md) · [search](https://mcp.film/capabilities/search.md) · [remote-mcp](https://mcp.film/capabilities/remote-mcp.md)

## Sample tools

`mandatory_init` · `search_assets` · `read_comments` · `write_comments` · `manage_versions` · `upload_media` · `manage_shares` · `change_metadata`

## Field notes

Public beta as of 7 Oct 2026, per Adobe staff on the forum thread that announced a private beta on 29 Jul. Self-serve now, with no onboarding call, but expect beta churn. Anyone who configured it before 7 Oct should check they are on the /v1/mcp URL. Frame.io Legacy accounts are not supported at all. Adobe Managed Accounts can land in the wrong organization if a stale Adobe session is reused; the docs give a fix. Tools run with your own permissions, so uploads need Contributor access. The write surface is real: `delete_resources` permanently deletes everything except files and folders, which `restore_assets` can bring back. Adobe recommends approving each write or delete call, which is the correct default in front of a client's review project. Adobe's docs give click-through steps for Claude Desktop, ChatGPT, Cursor, VS Code and Copilot CLI, but not a Claude Code command. The command above is the standard remote-HTTP form against the documented URL, and the endpoint's OAuth discovery document answers (checked 10 Oct 2026). There is no source repo, and the docs do not cover MCP-specific pricing; usage counts against your Frame.io plan. Supersedes the community `frameio` entry for every account except Legacy ones.

## Verification

- Status: Freshly checked (checked today)
- Added: 2026-10-10
- Last verified: 2026-10-10
- Machine JSON: https://mcp.film/api/mcps/frameio-official.json

## Links

- Site: https://frame.io/?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=frameio-official%3Asite
- Docs: https://next.developer.frame.io/platform/v4/docs/mcp/frame-io-mcp?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=frameio-official%3Adocs

---

Structured data: https://mcp.film/api/mcps/frameio-official.json · Directory: https://mcp.film
Canonical: https://mcp.film/mcps/frameio-official/
Hosted directory MCP: https://mcp.film/mcp