Local stdio MCP server over the Frame.io v4 API (Adobe)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"frameio-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# frameio-mcp A local **stdio MCP server** over the [Frame.io v4 API](https://developer.adobe.com/frameio/), built with [FastMCP](https://github.com/PrefectHQ/fastmcp) on top of the official [`frameio`](https://pypi.org/project/frameio/) Python SDK. It lets an MCP client (Claude Desktop, Claude Code, etc.) browse workspaces/projects/folders, upload footage, leave timestamped review comments, and create share links. > **Most people don't need this README.** To use it in Claude Code, install the > plugin from the marketplace (see the [repo root README](../../README.md)) and > run the `frameio-setup` skill. This document covers running the server > **standalone** (without the plugin) for development, and the full tool list. > Dev `uv` commands below assume you're in this directory (`plugins/frameio-mcp/`). ## How auth works Frame.io uses **Adobe IMS** OAuth. This server uses an **OAuth Single-Page App (SPA)** credential — a *public* client (no secret) with PKCE — and stores the resulting tokens in `~/.frameio-mcp/tokens.json` (mode `0600`). Access tokens auto-refresh via the refresh token granted by the `offline_access` scope, so you log in rarely. ### One-time setup in the Adobe Developer Console 1. In your Frame.io project, add an **OAuth Single Page App** credential. 2. Scopes: `openid, profile, email, offline_access, additional_info.roles`. 3. Redirect URI: **`https://localhost:8723/callback`** (must match exactly). 4. Copy the credential's **Client ID**. ### Install & log in ```bash uv sync # install deps uv run frameio-mcp login --client-id <YOUR_SPA_CLIENT_ID> ``` A browser opens for Adobe sign-in. Because Adobe requires HTTPS even on localhost, the temporary callback server uses a self-signed cert — your browser will warn "connection is not private." Click **Advanced → Proceed to localhost**. That's expected and only happens at login. Check state anytime: ```bash uv run frameio-mcp status uv run frameio-mcp logout …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.