The 7 Best MCP Servers for Video Production in 2026 (Ranked for Filmmakers Using Claude or ChatGPT)

Key Takeaways

• Storyflow ranks first for video production because it is the only server in this list with purpose-built production tools: one call builds a row of shot cards, another builds a strip board with a wall per shoot day, and the assistant reads the same board back later, including what changed and who changed it.
• Frame.io's MCP server moved from private to public beta on 7 October 2026, per Frame.io's own forum announcement. It lets an assistant navigate projects, read review comments, create shares, search and handle uploads. It is the pick for post-production, and it does nothing for a shot list.
• Boords runs an official MCP server at app.boords.com/mcp on every plan during its beta. The assistant writes scripts, builds storyboards from them, reorders frames and reads client comments. Boords' own image generation is not available over the connection.
• Notion, Asana and monday.com all publish official servers. They hold production data as pages, tasks and board items, which suits tracking and wikis and does not produce a strip board or a shot card.
• Claude's Google Drive connector searches and reads the scripts, budgets and PDFs you already have. It extracts text only, so it reads a script and cannot watch a cut.
• We found no MCP server or assistant connector published by StudioBinder, Celtx or Movie Magic Scheduling. An assistant's work reaches those tools by copy and paste.
• Storyflow's connector runs on your own assistant's model, so it does not spend Storyflow AI credits, and Plus, Pro and Max have no MCP limit.
• Most productions need two servers, not seven: one that holds the plan before the shoot (Storyflow) and one that holds the cut after it (Frame.io).

What an MCP Server Changes on a Production

You have probably already asked Claude or ChatGPT for a shot list. It gave you a decent one, as a block of text in a chat window. Then the location changed, the director cut two setups, and the version everyone agreed on was somewhere in a conversation only you can open. An MCP server fixes exactly that gap: it lets the assistant write into, and read from, the tool where the production actually lives.

A chat window is not a production office

A chat holds one person's conversation. A production is ten people who need the same schedule. Without a connector, every useful thing the assistant writes has to be retyped or pasted into the tool the crew opens, and every change made in that tool has to be pasted back before the assistant knows about it. Model Context Protocol (MCP) is the open standard that removes the pasting. A vendor publishes a server, you add its address to your assistant once, sign in, and the assistant gets a set of tools: list the projects, read this board, add these rows, build this schedule. Our explainer on apps, connectors and MCP servers covers the vocabulary; this post is about which servers are worth adding when the work is a film or a video.

Production paperwork has a shape that generic tools flatten

A strip board is not a table. It is a set of shoot days, each holding scenes in shooting order, coloured by interior or exterior and day or night, totalled in pages. A shot list in card form is a frame, a size, a checklist of coverage and the gear for that setup. A call sheet is a page with a fixed layout that a crew member reads in ten seconds. A server that only creates rows and pages can store the information in all three, and it cannot give you the document. That difference decides most of this ranking.

Three jobs a production needs connected

Every production, from a two-person brand film to an indie feature, needs an assistant to reach three kinds of place:

• The plan: breakdown, shot list, storyboard, schedule, call sheet. This is pre-production, and it is where an assistant saves the most typing.
• The files: the script, the budget spreadsheet, the location agreements, the release forms. Mostly documents and PDFs in a drive.
• The cut: versions, review comments and share links in post-production.

No single server covers all three. The ranking below is built around which job each server does and how well.

How We Ranked the Best MCP Servers for Video Production

A ranking with no published method is an opinion with a number on it. Six criteria, weighted for a filmmaker or producer running a real shoot, decide the order here. Storyflow is our product, so the weights are printed in full and you can disagree with any of them.

Production-document fit (30 percent)

Can the assistant build the documents a production runs on, in their real shape: shot list, storyboard, strip board, call sheet? A server with a dedicated tool for a production document scores above one that can only approximate it with rows. This carries the most weight because it is the job the target question asks about.

Phase coverage (20 percent)

How many of the five phases (development, pre-production, the shoot, post-production, delivery) does the server help with? A server that does one phase very well can still rank high; one that touches none of them cannot.

Read-back and change tracking (15 percent)

Productions change daily. Can the assistant read the current state in a new chat, and can it tell what changed? A server that only writes is half a server.

Setup and client reach (15 percent)

Does it work in both Claude and ChatGPT? Is it a remote server with sign-in, or something you install and feed an API key? How many steps before the first useful request?

Permission control (10 percent)

Can you limit what the assistant sees, and make it read-only? A client's unreleased campaign is on these boards. Per-project scope and a read-only mode matter more here than in most categories.

Cost for a small crew (10 percent)

What does it cost a one to five person team to use the server, including any plan gate on the server itself? Prices come from each vendor's own page, fetched on 10 October 2026.

What we did not weigh

We did not score generative video or image quality (none of these servers is a video generator), and we did not score tenure: every remote MCP server is new. We also ranked only servers published by the vendor of the product they connect to. Community-built servers exist for many tools, and they usually ask for an account-wide API key, which is a different risk decision from signing in to an official one.

Comparison Table: The Best MCP Servers for Video Production in 2026

Sources for every cell are linked in the reviews below. "Not stated" means the vendor page we read did not say, not that the feature is missing.

The 7 Best MCP Servers for Video Production, Reviewed

Each review follows the same order: verdict, who it suits, price, why it ranks where it does, strengths, limits. Skim the verdict lines first.

1. Storyflow

Verdict: the server that lets your assistant build the production's paperwork in its real shape, on one board the whole crew can open.

Best for: producers, directors and small production companies who plan in Claude or ChatGPT and need the shot list, schedule and call sheet to exist somewhere other than the chat.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 annual ($19 monthly), Max $39 annual ($49 monthly). Storyflow is paid-only during early access; its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. See Storyflow pricing.

Storyflow is a visual project planning workspace: an infinite canvas board that holds notes, tables, documents, images, moodboards, storyboards, mind maps, kanban, charts and slide decks. Its MCP server lives at https://mcp.storyflow.so/mcp and works with any assistant that can add a remote MCP server, including Claude, ChatGPT, Gemini, Grok, Claude Code, Cursor and Perplexity.

Why it ranks first. Two of its tools exist for film work and nothing else. The shot card tool builds a whole shot list in one call: a connected left-to-right row with one card group per shot, each holding a frame, short chips (size, light, camera), a "Shots required" checklist, a scene-direction note and an equipment note, with an arrow to the next shot. One call takes up to 60 shots. The strip board tool builds the shooting schedule in one call: a column per shoot day, a coloured strip per scene in shooting order, each day totalled in pages and eighths, with the industry colour code for interior or exterior and day or night applied by the tool. One call takes up to 30 shoot days. No other server in this list has a tool whose output is a strip board.

The rest of the paperwork. The assistant also builds tables (breakdown, budget, contacts), documents (treatment, director's notes), mind maps, diagrams and slide decks. A call sheet is built as a page deck on the board that you edit and export as one PDF. A kanban for post tasks is a row of column walls holding tickets, built with the same section tool as the tables. What the assistant adds appears live on a board you have open, and in clients that support MCP apps the real board is shown inside the chat.

What it reads. Boards, notes, documents and files, plus what changed on a board and who changed it, over the last day, the last week or the last month. On a production that is the question you ask every morning: "what changed on the schedule board in the last day?"

Strengths

• Dedicated shot card and strip board tools, each one call for the whole document.
• Everything lands on one board, so the shot list sits beside the references and the schedule it belongs to.
• Change tracking with names, in fixed windows of a day, a week or a month.
• At sign-in you pick which projects the assistant may use and whether it may make changes at all.
• Runs on your assistant's own model, so no Storyflow AI credits are spent; no MCP limit on Plus, Pro or Max.

Limits

• It does not send call sheets or track who confirmed. You export the PDF and send it yourself.
• The connector cannot generate images and cannot read comment threads. Frames are your own pictures, pictures added from web addresses, or empty placeholders you fill.
• A photo attached in the chat does not reach Storyflow; the assistant gives you an upload link.
• Browser only: no mobile or desktop app, no offline mode. On a set with no signal, export first.
• A free invited account is capped at 25 actions a week (every read and change counts as one), resetting Monday UTC. Connections expire after 30 days.

Try it: connect Storyflow to Claude or ChatGPT, then ask for a shot list from your script as shot cards. The step-by-step version is in how to make a shot list with ChatGPT or Claude.

2. Frame.io

Verdict: the server for everything after "cut", and the newest one in this list.

Best for: editors, post supervisors and producers whose review rounds already run in Frame.io.

Pricing: per Frame.io's pricing page, Free is $0 for up to 2 members with 2GB of storage, Pro is $15 per member a month (up to 5 members, 2TB included) and Team is $25 per member a month (up to 15 members, 3TB included), with a 13 percent discount on annual plans and custom Enterprise pricing. The announcement does not say which plans include the MCP server.

Frame.io announced its MCP server on its developer forum on 29 July 2026 as an experimental server in private beta. The post was edited on 7 October 2026 to say the server is now in public beta and that you can get started directly, without onboarding through the Frame.io team first, with connection instructions for Claude, ChatGPT, Cursor, VS Code and the GitHub Copilot CLI.

Why it ranks second. It owns a phase nothing else here touches. Per the announcement, a connected agent can navigate workspaces and projects, read comments, create shares, search and handle uploads. Frame.io is plain that these are the same endpoints its API already exposed; the new part is that an assistant can chain them. For a producer that means requests like "list every unresolved comment on the v2 cut and group them by picture, sound and graphics" stop being an afternoon of scrolling. It ranks below Storyflow only because the criteria weight production documents most, and Frame.io builds none.

Strengths

• The only server here that reaches review comments on a cut.
• Creating shares from the assistant suits the delivery phase: one request per stakeholder link.
• Published by the vendor, with setup documented for both Claude and ChatGPT.
• A free Frame.io plan exists for two members.

Limits

• Public beta, ten weeks after a private one. Tool names and behaviour can still change.
• No pre-production documents of any kind.
• The announcement does not state plan requirements, a read-only mode or rate limits. Check the linked documentation before you rely on it for a client delivery.
• The assistant reads comments as text. It does not watch the video.

Trade-off: if your work ends at the shoot (a DP, a first AD), skip it. If you deliver finished films, this is the second server to add. Our comparison of Frame.io, Ziflow, Filestage and Storyflow for client approvals covers the review tools themselves.

3. Boords

Verdict: the best server when the deliverable is a storyboard a client has to approve frame by frame.

Best for: agencies and animation or commercial teams whose storyboards and sign-offs already run in Boords.

Pricing: per Boords' pricing page, there is a free plan (5 active storyboards, 3 active scripts, 8 one-off sample AI image credits); Solo is $39 a month or $26 a month billed annually for one user, Pro is $75 or $50 for up to 5 users, Team is $125 or $85 for up to 10, and Agency is $250 or $165 for up to 30.

Boords documents its MCP server on its connections page. The address is https://app.boords.com/mcp. In Claude you add Boords from the connector directory; ChatGPT needs ChatGPT Plus or above with Developer mode. You sign in to Boords and approve either Read or Read and write access; no API key is involved.

Why it ranks third. The tool list is deep and specific to pre-production. Per the same page, the assistant can list, create and update projects; create, edit, duplicate, archive and restore scripts and save versions; create storyboards, including from a script; add, update, delete, reorder and attach images to frames; manage the asset library; and read, add, update and delete comments, with mentions. Anything destructive needs an explicit confirmation before it runs. Reading client comments is the feature the top-ranked server lacks. Boords ranks below Frame.io because it covers one document (the storyboard and its script), and below Storyflow because it has no schedule, shot list card or call sheet.

Strengths

• Script to storyboard in one request, in a tool clients already know how to approve.
• Comments are readable and writable by the assistant.
• Read-only connection option, and deletes ask for confirmation.
• Boords says the server is available on every plan, including Free, at no extra cost during beta.

Limits

• Boords states that its own image generation, restyling and styles are not available through a connection. The assistant arranges frames; it does not draw them.
• A connection can see and change what your account can, across all your teams. There is no per-project scope.
• Boords notes that usage limits may apply in the future.
• No strip board, call sheet or budget.

Trade-off: choose Boords when sign-off on frames is the contract milestone. Choose a board when the storyboard is one of six documents that have to agree with each other. Storyflow vs Boords compares the two products directly.

4. Notion

Verdict: the best server for a production wiki and a database-shaped breakdown.

Best for: production companies that already keep contacts, locations, vendor lists and project pages in Notion.

Pricing: per Notion's pricing page, Free is $0, Plus is $10 per member a month billed annually ($12 monthly) and Business is $20 per member a month billed annually ($24 monthly).

Notion's MCP server is an official remote server with OAuth sign-in. Its supported tools page lists tools to search, fetch, create and update pages, create databases and views, move and duplicate pages, and read and add comments.

Why it ranks fourth. A script breakdown is honestly a database: one row per scene, with properties for location, cast, props and page count. Notion's server handles that well, and a filtered view per location is one request. It falls behind the top three on document fit: the same scene rows cannot become a strip board with day totals, and a shot list is a table with no frames beside it. It ranks ahead of the pure task trackers because a production wiki (contacts, locations, vendor terms) is real production content.

Plan gates to know. The supported tools page says AI search needs a Business or Enterprise plan with Notion AI, meeting-notes queries need Business or higher with Notion AI, and SQL-style queries across data sources are unlimited only on Business and Enterprise with Notion AI, with a shared per-workspace allowance on other plans.

Strengths

• Mature database tools: properties, views, filters.
• The assistant can read and add comments on pages.
• Many producers already have a Notion workspace to point it at.

Limits

• Linear pages and tables only: no strip board, shot card or storyboard layout.
• Several tools are gated to Business with Notion AI.
• Every tool call counts toward Notion's standard API rate limits.

Trade-off: keep Notion for what does not change per project (the company wiki) and put the per-shoot paperwork where it can take its real shape. Notion vs StudioBinder vs Storyflow for video producers goes deeper on that split.

5. Google Drive

Verdict: not a planning tool, and still the connector most productions should turn on, because the script and the budget are already there.

Best for: anyone whose scripts, budgets, releases and location agreements live in Drive.

Pricing: Drive storage comes with a Google account; this review covers the connector, not storage plans.

This review describes Claude's Google Drive connector, the one whose documentation we could read. Per Anthropic's Google Workspace connectors article, Claude can search Drive, read Google Docs, Sheets, Slides, PDFs, images and Microsoft Office files, look up file details and permissions, create folders and upload files, and share, move or trash files, asking for your approval first by default. The article says the connectors are available to all users on Claude and Claude Desktop. OpenAI's help pages refused our fetches, so check ChatGPT's own connector list for its equivalent.

Why it ranks fifth. It is a source, not a destination. The most valuable production use is giving the assistant the real script and the real budget instead of a summary, then having another server build from them. On its own it creates no production document, which caps its score on the heaviest criterion.

Strengths

• Reaches the files a production already has, with no migration.
• Mirrors your existing Google permissions.
• Approval prompts before share, move and trash actions.

Limits

• The article states that Claude extracts text content only, and images embedded in documents are not processed. A lookbook PDF comes through as its captions.
• The article lists no video formats. Do not expect it to review a cut.
• Documents must fit in the conversation's context window, so a long feature script plus a budget may need splitting.
• Live editing of Docs, Sheets and Slides is handled by separate connectors, not Drive.

Trade-off: turn it on, use it to feed the other servers, and do not try to run the shoot from a folder tree.

6. Asana

Verdict: the best task server for post-production and delivery lists with owners and due dates.

Best for: in-house video teams and production companies that already assign work in Asana.

Pricing: per Asana's pricing page, Personal is free for up to 2 users, Starter is $10.99 per user a month billed annually ($13.49 monthly) and Advanced is $24.99 per user a month billed annually ($30.49 monthly).

Asana's MCP server documentation gives the V2 server address as https://mcp.asana.com/v2/mcp, with OAuth sign-in and Streamable HTTP. It is offered as the Asana app in Claude and in ChatGPT, with separate setup for Claude Code, Codex, Cursor and VS Code. The older beta server is deprecated.

Why it ranks sixth. Asana describes the server's job as creating and managing tasks and projects in natural language, generating reports and summaries, and analysing project data. That is exactly what post-production needs: 40 deliverables, each with an owner and a date. It does nothing with a script, a frame or a schedule in production terms, so it scores low on document fit and sits below the file connector that feeds every phase.

Strengths

• Official, with first-party apps in both Claude and ChatGPT.
• Status summaries on request: "what is overdue on the campaign delivery project?"
• A free plan for two users.

Limits

• Asana does not publish a fixed tool list on the setup page; it tells you to list tools from your client.
• The page does not state a plan requirement or a read-only mode. Admin controls to allow or block MCP clients are described for Enterprise tiers.
• Tasks, not production documents.

Trade-off: good second or third server for a team already in Asana. If you are choosing a tracker from scratch for video work, read Asana vs monday for video teams first.

7. monday.com

Verdict: the widest tool list of the trackers, best for a company running many productions at once.

Best for: production companies and agencies tracking a slate of projects on monday.com boards.

Pricing: monday.com's pricing page showed us euro prices: Free for up to 2 seats (3 boards), then Basic at 9 euros, Standard at 12 euros and Pro at 19 euros per seat a month billed annually, with paid plans starting from 3 seats. The page says prices depend on your billing country, so check it for your own currency.

monday.com's Platform MCP overview gives the hosted server as https://mcp.monday.com/mcp and describes more than 60 tools for reading and writing monday.com data: creating items, updating columns, querying boards. Its compatible clients page lists Claude, ChatGPT, Cursor, Microsoft Copilot, Gemini CLI, Mistral and Perplexity among others, and says to use Streamable HTTP only.

Why it ranks seventh. For one shoot it is more structure than you need, and none of it is film-shaped. For a company with 15 jobs in flight it is the right kind of structure: one board of projects with status, budget and delivery date columns an assistant can query. It ranks last of seven because it scores lowest on document fit, and because of one cost detail: monday.com states that MCP tool calls run as API requests and count toward your account's daily API call limit.

Strengths

• More than 60 documented tools.
• Account admins approve any client outside monday.com's pre-approved list before it can connect.
• Broad client list.

Limits

• Tool calls count against the account's daily API limit.
• Paid plans start at 3 seats, which is awkward for a solo filmmaker.
• No production documents.

Trade-off: add it when the question you ask most is "where is every job?" and not "what are we shooting on Thursday?".

Which Server Covers Which Production Phase

Rankings hide the fact that these servers barely compete: they work at different times. Read this table down the column for the phase you are in.

Development and pre-production: one server does most of the work

Before the shoot, the documents depend on each other. The breakdown feeds the shot list, the shot list feeds the schedule, the schedule feeds the call sheet. A server that keeps them on one surface wins this phase, which is why the criteria favour Storyflow. If the storyboard has its own approval round with a client, Boords joins for that one document.

The shoot: read more than you write

During the shoot nobody should be building new documents by chat. The useful requests are reads: what changed on the schedule in the last day, which shots on tomorrow's cards have no location confirmed. Any server with read-back helps; change tracking helps most.

Post-production and delivery: Frame.io plus a tracker

Once there is a cut, the centre of gravity moves to review comments and deliverables. Frame.io reads the comments; Asana, monday.com or a kanban on the production board holds the resulting tasks. How to run a video review round with a client covers the human side of that round.

Production Tools With No Connector We Could Find

Some of the most used film tools are missing from this ranking, and you deserve to know that is a finding, not an oversight. We searched each vendor's site and the public web on 10 October 2026.

StudioBinder

We found no MCP server and no ChatGPT or Claude connector published by StudioBinder. It remains a full production suite in its own right; an assistant's shot list or schedule reaches it by retyping or paste. If that gap matters, see our StudioBinder alternatives.

Celtx

We found no MCP server or assistant connector published by Celtx. Scripts written there can be exported and given to an assistant as a file, which is a one-way trip.

Movie Magic Scheduling

We found no MCP server or assistant connector for Movie Magic Scheduling from Entertainment Partners. If a financier, bond company or studio names Movie Magic as the required format, that requirement outranks every connector in this post. Our film scheduling software guide covers when that applies.

Storyblocks and ElevenLabs: real servers, different job

Two servers are useful to video people and sit outside "running a production". Storyblocks describes an MCP connector on its own site that lets Claude or ChatGPT search and download from its stock library; its pages would not load for our fetches, so we could not confirm plan details and left it unranked. ElevenLabs runs a hosted MCP server at api.elevenlabs.io/v1/mcp with OAuth sign-in, according to its official repository, which now marks the older local server as deprecated. That one is for voice and audio generation, not planning.

Milanote

We found no connector for Milanote, and it lists no AI features. It remains a pleasant moodboard tool that an assistant cannot write to.

Worked Example: A Two-Day Brand Film Run Across Four Servers

This is an illustrative example, written to show the order of work and the kind of numbers involved. The production, counts and tallies are invented, not measured.

The job: "Harbour Light", a 90-second brand film for a coffee roaster. Three script pages, nine scenes, two shoot days, a crew of seven, one client contact. The producer uses Claude with four servers connected: Storyflow, Google Drive, Boords and Frame.io.

Day 1 of prep: the script becomes a breakdown

The script is a Google Doc. You ask Claude to read it from Drive and build a breakdown table on a new Storyflow board called "Harbour Light: Production": one row per scene with slugline, interior or exterior, time of day, page count in eighths, cast and props. Nine rows come back. You correct one page count (scene 4 is 4/8, not 3/8) on the board by hand.

Day 2 of prep: shot cards and a storyboard for the client

You ask for a shot list as shot cards from the breakdown and the director's notes: 24 shots, each with its size, coverage checklist, direction and gear. The frames are placeholders, because the connector does not generate images; the director drops phone photos from the recce into eleven of them. The client's contract includes storyboard approval, so you ask Claude to create a Boords storyboard from the same 24 shots. The client comments on four frames in Boords, and Claude reads those comments back and lists the four changes.

Day 3 of prep: the strip board and the call sheets

You ask for a strip board: two days, interiors grouped, the harbour exteriors at the start of day two for the light. The tool colours the strips and totals each day.

Then one request per day builds a call sheet as a page deck on the board. The assistant was told to leave unknowns blank, so the deck comes back with three visible gaps: the gaffer's phone number, the day-two parking address and the nearest hospital for the harbour. You fill them, export each deck as a PDF and send it yourself.

The shoot and the edit

On the evening of day one you ask what changed on the board in the last day. Claude reports that the first AD moved scene 9 to day two and edited two shot cards. A week later the editor uploads v1 to Frame.io. The client and the director leave comments; you ask Claude to read them and turn them into tickets on a post kanban on the Storyflow board, grouped by picture, sound and graphics.

What the example adds up to

The right-hand column matters only on a free invited account, where every read and change counts toward 25 actions a week. In this illustrative tally the 23 actions fit, but only just if everything lands in one week, with two left for a correction. Here the post kanban comes a week later, so the prep week uses about 20; on Plus, Pro or Max there is no MCP limit to count.

Prompts You Can Copy

Use these as written, then change the nouns. Each names the server so the assistant picks the right tools.

Two rules make all of these work better. Name the board or project exactly, and tell the assistant where numbers must come from. An assistant that is allowed to guess a page count will guess one.

What It Costs: Three Production Stacks Priced Out

Prices are the vendors' published figures on 10 October 2026, before tax, and exclude your Claude or ChatGPT plan. Frame.io figures are its per-member monthly prices; Storyflow, Boords and Asana figures are the monthly equivalent on annual billing.

Three things keep these numbers honest:

• Storyflow has no per-user pricing. Anyone a paid member invites to a board joins free, with 25 MCP actions a week on the invited account; Max adds a team workspace with roles and permissions.
• Claude's Free plan allows one custom connector. In the solo stack that slot goes to Storyflow, and Google Drive is one of Claude's own built-in connectors. ChatGPT needs ChatGPT Plus or above with Developer mode to add a custom server.
• The largest line in the big stack is the review tool, not the planning tool. That is normal for video: storage and seats in post cost more than paperwork.

Which MCP Server Should You Connect First?

Start from the phase that hurts, not from the longest feature list.

• If the pain is "the shot list and schedule live in a chat", connect Storyflow first.
• If the pain is "feedback on the cut is scattered", connect Frame.io first.
• If the pain is "the client will not sign off the storyboard", connect Boords first.
• If the pain is "nobody can find the vendor contacts", connect Notion or Google Drive first.
• If the pain is "deliverables slip", connect Asana or monday.com first.

For a solo filmmaker or a two-person team

Storyflow and Google Drive. Drive feeds the script in; Storyflow holds everything built from it. Add Frame.io's free plan when the first cut exists. That is the whole stack. In prep it needs only one custom connector (Storyflow), which is what Claude's Free plan allows; check how Frame.io's server is added in your client before you count on a second one.

For a producer at a production company

Storyflow for each job's board, Frame.io for review, and whichever tracker the company already pays for. Do not introduce a second tracker because it has a server; the cost of two task lists is higher than the cost of a missing connector. The best AI tools for producers covers the rest of the kit.

For an agency video team with client approvals

Boords for storyboard sign-off, Frame.io for cut sign-off, Storyflow for the plan that connects the two. Give the assistant read-only access wherever client comments live, so a misread request cannot rewrite approved work.

For an indie feature

Storyflow for breakdown, shot cards and the strip board during prep, with Google Drive for the script and agreements. If your first AD schedules in Movie Magic, treat the strip board on the board as the working draft and Movie Magic as the record. Indie film project organisation with Claude or ChatGPT walks through a full prep.

How to Connect Storyflow to Claude or ChatGPT

The address is the same in every client: https://mcp.storyflow.so/mcp. Steps for every supported assistant are in the help article.

Claude

1. Open Customize, then Connectors.
2. Click Add, then Add custom connector.
3. Name it Storyflow, paste the address and click Continue.
4. Choose Sign in now, click Add, and sign in to Storyflow.

ChatGPT (web)

1. You need ChatGPT Plus or above with Developer mode. Turn Developer mode on under Settings, then Security and login (an admin does this on Business and Enterprise).
2. Go to chatgpt.com/plugins and click the plus button.
3. Name it Storyflow, choose Public endpoint and paste the address.
4. Create it and sign in to Storyflow.

What to choose at sign-in for a production

Pick the projects, not "all projects", when a client's work is in the account. Allow changes for the producer's own connection and leave it read-only for anyone who only needs answers, such as a client-side stakeholder. Access to documents outside projects starts off when you pick projects; leave it off unless the script lives there. You can disconnect in Settings, Connected apps, and access ends within a minute.

Common Mistakes When Filmmakers Connect MCP Servers

Most of these cost a morning. One of them can cost a shoot day.

Letting the assistant schedule from memory

A strip board built from "the script we discussed earlier" will contain scenes that were cut. Make every schedule request point at the breakdown table or the script file by name.

Accepting invented phone numbers and addresses

An assistant asked for a "complete" call sheet will complete it. Say "leave blanks and list them" in the request. A visible blank gets filled; a plausible fake number gets a crew member lost at 6 a.m.

Connecting every server on day one

Seven servers means seven sets of tools the assistant has to choose between, and it will sometimes put the shot list in the task tracker. Start with two. Add a third when a specific request fails.

Giving write access where approvals live

If a client approved frames in Boords or left notes in Frame.io, connect read-only there where the server offers it. The plan can be rebuilt; an overwritten approval is an argument.

Pasting API keys into unofficial servers

A community server that asks for an account-wide API key can do anything your account can, with no project scope and no sign-in screen. Every server ranked here is published by its vendor or, for Google Drive, offered inside the assistant itself. Keep it that way for client work.

Treating the board as the delivery mechanism

A board link is for the people planning. The crew gets a PDF. Storyflow does not send call sheets or track confirmations, and neither does any other server here; export and send through the channel your crew already answers.

Forgetting the beta label

Frame.io's server is in public beta and Boords calls its server a beta too. Do not build a delivery deadline on a tool whose behaviour can change next week without a manual fallback.

When Storyflow Is Not the Right Choice

Storyflow ranks first on these criteria, and it is the wrong server for several real production jobs:

• Sending call sheets and tracking confirmations. Storyflow builds the pages; it does not text them or record who opened them. Use a dedicated call sheet tool for that; our call sheet software guide compares them.
• Reviewing a cut. It has no frame-accurate video review. Frame.io does.
• Formal, versioned approvals. There is no approve button and no approval audit trail. If sign-off is contractual, Boords or a proofing tool is the record.
• A mandated scheduling format. If the bond company wants a Movie Magic file, a strip board on a canvas is a draft.
• Reading comment threads through the connector. The assistant cannot read comments on a Storyflow board. Boords, Notion and Frame.io expose comments to an assistant.
• Generating frames through the connector. Image generation is in Storyflow's built-in agent on Pro and Max, not in the MCP server.
• Working with no signal. Storyflow is browser only, with no mobile or desktop app and no offline mode.
• A $0 setup today. Storyflow is paid-only during early access; its Free plan launches before the end of 2026. Frame.io, Boords, Asana and Notion all have free plans now.
• Sorting and calendars. The canvas does not sort a table and has no calendar tool; dates live in table date cells, tickets and kanban, with rows kept in date order by you or the assistant.

A Production Board Template You Can Ask For

You do not need to design the board. Ask the assistant to build this layout once, then reuse it for every job.

The seven sections, left to right

The prompt that builds the empty template

Create a new Storyflow project called "(Job name): Production" and build these sections left to right on its board: a Brief document, an empty References area, a Breakdown table with columns scene, slugline, INT or EXT, time, pages, cast, props; a placeholder for the shot list; a placeholder for the strip board; a Contacts table with columns role, name, phone, email, call time; and a Post kanban with columns To do, In progress, Client review, Done. Leave every cell empty.

The one rule that keeps the board right

The breakdown table is the source. Shot cards, strip board and call sheets are built from it, never from the chat. When a scene changes, change the row first, then ask the assistant to rebuild what depends on it. Our film shoot planner and shot list software pages show the same board built by hand.

The Bottom Line

Pick servers by phase. Before the shoot, the documents have to agree with each other, and the server that builds them in their real shape on one board is Storyflow: shot cards, a strip board, call sheet pages, and a change log you can ask about every morning. After the shoot, Frame.io's new server is the one that reaches the comments on the cut. Boords earns its place when a storyboard needs a client's sign-off, and Notion, Google Drive, Asana and monday.com are worth connecting only if your production already lives in them.

What none of them replaces is the producer's judgment about what is true. The assistant builds fast and guesses confidently, so point every request at the script and the breakdown, ask for blanks instead of inventions, and keep a PDF for the crew. If you want to try the first step, connect Storyflow and ask for your next shoot's shot list as cards.