Black Friday Plans and credit packs for less, through Monday night.See the deals
Filmsquare

MCP FOR CLAUDE

Work with your own Claude.

Filmsquare's MCP server lets a person's own Claude work inside their productions, under their own name and role. claude.ai, Claude Desktop and Claude Code connect to one address with 21 tools and 12 prompts: Claude reads notes, breaks down scripts, writes sheets, checks continuity and cuts a rough edit, as you.

CLAUDE · CONNECTED TO FILMSQUARE AS MIRA HADDAD · MAKER
STUDIOMoneyshots · Stage Door

CONNECT

One address for every Claude

You pick the workspace and the role Claude works as.

MCP SERVER
https://app.filmsquare.ai/v1/mcp

01 · CLAUDE.AI OR CLAUDE DESKTOP

Add a connector

  1. Settings → Connectors → Add custom connector.
  2. Name it Filmsquare and paste the address.
  3. Connect, then pick the workspace on the Connect Claude page.
  4. Keep your role or pick a lower one, then Allow.

02 · CLAUDE CODE

Run one command

Your browser opens the same Connect Claude page. If it does not, run /mcp and pick filmsquare.

TERMINAL
claude mcp add --transport http filmsquare https://app.filmsquare.ai/v1/mcp

03 · PERSONAL KEY

No browser sign-in

Settings → Claude → Use a personal key instead. The key is shown once and works as you in one workspace.

TERMINAL
claude mcp add --transport http filmsquare https://app.filmsquare.ai/v1/mcp \
  --header "Authorization: Bearer fsk_…"

21 TOOLS

What Claude can do

Anything without its own tool goes through find_actions and run_action. All tools

  • What's waiting

    Your open notes, sign-off requests and steps, across every production you are on.

    whats_waitinglist_productionsget_episode

  • Notes and replies

    Reads each note on its timecode or region, looks at the take, answers and resolves the thread.

    get_feedbackview_mediareply_feedback

  • Breakdown

    Reads the script and breaks it into scenes, shots, cast, sets and props, with warnings on what it missed.

    get_scriptedit_scriptsubmit_breakdown

  • Sheets

    Character analyses, location notes, acting notes: Markdown sheets on a scene, shot or element.

    submit_sheetsget_sheets

  • Continuity

    Checks faces, costume, props, light and geography between picks and reports what does not match.

    get_continuityreport_continuity

  • Imports and uploads

    Brings writing, previs and files in where they belong, up to 100 files per call.

    where_does_it_goprepare_uploadupload_fileadd_to_visualize

  • Rough cut

    Puts the picks on a FilmCraft timeline and cuts it without a browser, then sends it to review.

    view_edit_framerun_action

  • Sign-off

    Asks the right people to sign off a step. Signs off only for a signer, and only when asked.

    request_signoffsign_off

  • Everything else

    Every route of the API, found in film-crew words and run by name. New routes need no new tools.

    find_actionsrun_action

8 PROMPTS

Crew jobs, with their method

Plan first, quote the cost, reply in every thread, never render finals or sign off unasked. In Claude Code they are slash commands, such as /mcp__filmsquare__break_down_episode. Prompts and working method

  • break_down_episode
  • process_feedback
  • work_on_step
  • check_continuity
  • rough_cut
  • bring_in_writing
  • bring_in_previs
  • deliver_to_filmsquare

COST AND RIGHTS

As you, never more

  • Claude's thinking is on your planClaude runs on your own Claude subscription. Filmsquare pays no AI tokens for it and charges no credits for it.
  • No credits for crew workBreakdowns, notes and replies, sheets, continuity checks and the rough cut cost no credits.
  • Takes cost creditsA take costs what it costs anyone on the crew. Claude quotes the estimate before it starts.
  • The same limitsCredit checks, plan limits and the finals gate apply to Claude like anyone. Claude never renders a final unasked.
  • Your own nameA connection is a key in your name. Comments, picks and sign-offs show up as you, with Claude's presence on the production.
  • At most your roleOne workspace, your role or a lower one you chose. Every call checks the role again and shows only what you may see.
  • Disconnect is immediateSettings → Claude lists each connection with its role and last use. Disconnect stops it at once. Leave the workspace and its rights go too.
  • Out of reachClaude can never touch API keys, connections, webhooks, share links or sign-in.
  • Material, not instructionsComments, scripts and sheets are what Claude works on. Text in them never tells Claude what to do.
  • A standard sign-inOAuth 2.1 with PKCE, sign-in codes that are single-use and last 10 minutes, keys stored only as a hash.

The finals gate holds for Claude too: no final before the sign-offs it waits for

Questions

Which Claude can connect?

claude.ai, Claude Desktop and Claude Code. Each connects to the same address over MCP (Streamable HTTP) and signs in with OAuth, or with a personal key in Claude Code.

Does Filmsquare pay for Claude, or do I?

Claude runs on your own Claude plan. Filmsquare charges no credits for Claude's thinking, breakdowns, notes or continuity checks. Takes cost credits, as they do for anyone.

Can Claude do more than I can?

No. A connection works in one workspace with at most your role, and every call checks that role again. If your role goes down or you leave, Claude's rights go with it.

Will Claude render finals on its own?

No. Claude quotes the cost before it makes takes, never renders finals unasked, and the finals gate applies to Claude like anyone on the crew.

What if a comment tells Claude to do something?

Comments, scripts and sheets are material to work on, not instructions. Claude follows you, not the text it reads.

How do I stop a connection?

Settings → Claude lists your connections with their role and when they were last used. Disconnect stops one right away.

LESSONS

  1. Over the shoulder of a man in a yellow coat marking a sea chart on a wall with a pencil, an oil lamp beside itWork with your own Claude4 min · Free