Skip to content

FilmScribe in Cursor and VS Code your recordings become files in your project.

The FilmScribe connector works as an MCP server in Cursor and in VS Code, with GitHub Copilot in agent mode. Your editor's assistant reads your transcripts, chapters, hooks and clips, and you ask it to turn them into project files, like a Markdown post or the chapters on a page. If you allow it, it also fixes the transcript and organizes. It comes with Studio and Agency, trials of those plans included.

What you ask in your editor

From recordings to your repo

The connector supplies the data; writing the file into your project is your editor assistant's job. Lookups don't use your plan's hours.

You ask forWhat you getAccess
A post from a lessonThe transcript, to become Markdown in your projectRead
An event's chapters and momentsTitles and timestamps for the event pageRead
High-scoring suggested clipsTitle, timestamp, score and reason for eachRead
A link to a clip's videoA link that works for up to 24 hoursRead
Fixing a term in the transcriptThe fix made in FilmScribeWith permission
Creating or adjusting a clipThe clip saved to the fileWith permission
You stay in control

Your editor only sees and does what you approved

Login opens in your browser, on a FilmScribe screen that shows the assistant's name. By default access is read-only, and deleting or spending hours always wait for your yes.

The connector doesn't read any of your code. It only answers what the assistant asks FilmScribe for, and under Profile > Connections you see everything that was looked up or changed.

Your assistant canYour assistant can't
Read files, transcripts, chapters, hooks, scripts and clipsChange anything unless you allowed it when connecting
Create download links and timelines for your editorDelete or spend hours without your yes
Organize, create and edit, if you allow itTouch your subscription, payments or account details
Show the hours before importing or processingSee features outside your plan
Step by step

How to add FilmScribe to Cursor and VS Code

  1. 01

    Cursor: edit mcp.json

    Under Profile > Connections in FilmScribe, copy the Cursor configuration and paste it into ~/.cursor/mcp.json (create the file if it doesn't exist).

  2. 02

    Cursor: log in

    Save it. In Cursor's MCP settings, log in to FilmScribe when asked.

  3. 03

    VS Code: open the config

    Under Profile > Connections in FilmScribe, copy the VS Code configuration. Open the Command Palette (Cmd+Shift+P or Ctrl+Shift+P), run MCP: Open User Configuration, paste it and save.

  4. 04

    VS Code: start and approve

    Click Start above filmscribe and log in in your browser. To allow changes, tick “Also allow creating, editing and deleting” and click Allow.

In VS Code, it works with GitHub Copilot in agent mode. If the file already has other servers, add only the filmscribe block.

Recipes

What to ask in Cursor or VS Code

You ask “Read the transcript of lesson 3 and create posts/lesson-3.md with the cleaned-up text and the chapters as subheadings.” A blog post from a lesson The assistant reads the transcript and writes the file into your site's repo.
You ask “Generate a JSON file with the webinar's chapters and moments for the event page.” Chapters on the event page It pulls chapters and moments and builds the data the page uses.
You ask “List the episode's suggested clips scoring above 80 in a Markdown table with title, timestamp and reason.” A clip review table It lists the suggested clips with score and reason.
You ask “Replace Film Scribe with FilmScribe in the transcript of episode 8.” The brand name, right With permission, it fixes the term in the transcript, and the fix carries into captions.

The same connector works in ChatGPT, Claude and Gemini CLI. See the full connector →

Frequently asked questions

Does the connector work with GitHub Copilot?

Yes, in VS Code with GitHub Copilot in agent mode. Once you add the server and log in, Copilot gets FilmScribe's tools and uses them when you ask about your recordings.

Does FilmScribe read my code?

No. The connector only answers what your editor's assistant asks FilmScribe for, like a transcript or a list of clips. Writing files into your project is your editor assistant's job, with the permissions you already gave it.

I already have other MCP servers in the file. Now what?

Add only the filmscribe block inside mcpServers in Cursor, or inside servers in VS Code. Your other servers stay as they are.

Why would a creator use this in a code editor?

For anyone who runs a site, a blog or a course in code. A lesson's transcript becomes a post, a webinar's chapters become the event page and the clip list becomes a review table, without copying and pasting between windows.

Can the assistant change anything in my FilmScribe account?

Only if you tick “Also allow creating, editing and deleting” when connecting. Without it, it only reads. With it, deleting and spending hours still wait for your yes, and everything shows up under Profile > Connections.

Which plan includes the connector?

Studio and Agency, trials of those plans included. It isn't part of Pro. On the editor side, each one's MCP setup applies: in VS Code, with GitHub Copilot in agent mode.

Your recordings, one request away in your editor. No copy and paste.

Upload your footage, let us transcribe it and connect Cursor or VS Code under Profile > Connections.

See the result on your own recording before adding a card.