How to Use the Frame.io MCP in VS Code Copilot

Q: How do I share the Frame.io MCP configuration with my team in VS Code Copilot?

Simple. Create a .vscode/mcp.json file in your project's root directory, add the Frame.io server details, and commit it to Git. Everyone who pulls the repo will have the tools configured in Copilot.

Q: Can we automate adding QA comments to Frame.io assets using VS Code Copilot?

You can. A developer can instruct Copilot to use the addcomment tool as part of a manual or semi-automated workflow within their editor. It's a great way to log technical findings during development.

Equip your entire dev team with Frame.io tools inside VS Code, managed through your repo's configuration.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Frame.io MCP to VS Code Copilot

Create your Vinkius account to connect Frame.io to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Frame.io with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Standardize Team Access to Frame.io

Add the Frame.io MCP server to your project's `.vscode/mcp.json` file and commit it. Now, every developer on the team gets the same set of tools in Copilot Chat automatically. No individual setup required. This ensures your whole team is building against the same API reality. When someone asks Copilot to `list_projects`, they're getting the same live data as everyone else. It's consistency for your entire engineering org.

Write and Test Scripts with Copilot

Working on a Python script to process video feedback? Ask Copilot to get all comments for an asset with `list_asset_comments`. It will call the tool and provide the data you need to continue scripting. You can use this to quickly build and validate logic. For instance, get project metadata with `get_project_details` to confirm settings, then use `add_comment` to post a status update—all without leaving VS Code.

Your Team's Shared MCP Server for Frame.io

This isn't just for you; it's for the team. The shared configuration means a senior dev can build a workflow, and a junior dev can use it instantly. It becomes a central part of your dev environment, just like your linter or debugger. Use tools like `list_teams` and `list_accounts` to give Copilot context about your organization's structure. This helps it generate code that's aware of your specific Frame.io setup.

Setup guide

Set up Frame.io MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Frame.io MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Frame.io tools listed. Try asking: "List my recent Frame.io transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "frameio-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Frame.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Frame.io now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Frame.io MCP in VS Code Copilot

Simple. Create a `.vscode/mcp.json` file in your project's root directory, add the Frame.io server details, and commit it to Git. Everyone who pulls the repo will have the tools configured in Copilot.

Yes. Once configured, any team member can ask Copilot Chat to run the `get_project_details` tool. It returns the project's metadata right in the chat, perfect for quick reference while coding.

Centralized management. By defining the MCP server in the repo, you enforce a single source of truth for tools. It aligns with enterprise practices for environment consistency and security.

You can. A developer can instruct Copilot to use the `add_comment` tool as part of a manual or semi-automated workflow within their editor. It's a great way to log technical findings during development.

The connection is secure. The MCP server on Vinkius manages the auth token and makes direct, temporary calls to the Frame.io API on your behalf. No sensitive data like asset comments or project lists is ever logged or stored by the server.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript