Frame.io V4 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADOBE_CLIENT_ID | No | Adobe Developer Console Native App client ID used for public-client refresh without a client secret. | |
| ADOBE_REFRESH_TOKEN | No | Adobe OAuth refresh token, if issued, used along with ADOBE_CLIENT_ID to refresh access without a client secret. | |
| FRAMEIO_ACCESS_TOKEN | No | Short-lived Frame.io access token returned after completing the Adobe OAuth login. Sufficient for a session. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_connectionA | Verify Frame.io V4 OAuth by calling GET /v4/me. |
| search_toolsC | Search all operations in the official Frame.io V4 OpenAPI catalog. |
| get_tool_schemaB | Get official parameters and referenced schemas for one Frame.io V4 operation. |
| invoke_toolC | Invoke one operation from the official Frame.io V4 OpenAPI catalog. DELETE requires confirm=true. |
| upload_local_fileC | Upload a local file through Frame.io V4 presigned URLs and return its upload status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.