Connect your assistant

The connector runs on your machine: nothing is sent elsewhere and it needs no account. Add this to your assistant's connectors (its “MCP” configuration):

{
  "mcpServers": {
    "cutscene": {
      "command": "npx",
      "args": [
        "-y",
        "cutscene-mcp"
      ],
      "env": {
        "CUTSCENE_DIR": "/path/to/your/films"
      }
    }
  }
}

It works with an assistant installed on your computer (a desktop app or a code editor), not with its version in a web browser, and it needs Node.js 20 or later (nodejs.org). The first time, it downloads itself, then the browser that draws the pictures (about 100 MB): allow a minute or two.

In what you just pasted, replace /path/to/your/films with a folder on your machine, as a full path. Your films are written there, each one a .cutscene.json file.

With a key from your account

Without a key the free plan applies: base pieces, 1080p export in 16:9 and vertical, with an end line. With a key from your account, your assistant exports as your plan allows. Add these two variables next to CUTSCENE_DIR; make the key on the page API keys.

{
  "CUTSCENE_DIR": "/path/to/your/films",
  "CUTSCENE_APP_URL": "https://app.cutscene.studio",
  "CUTSCENE_TOKEN": "cs_…"
}

Its settings

Environment variables, in your assistant's configuration:

CUTSCENE_DIR

The folder of your films: one .cutscene.json file per film, the pictures you put in, the exports, the versions and the bin.

CUTSCENE_TOKEN

Your API key (it starts with cs_): your plan then decides what exports, and your pieces can be shared.

CUTSCENE_APP_URL

Cutscene's address, with the key; alone, it is enough to read what others shared.

CUTSCENE_COUNT

“off”: do not count the use of pieces from your assistant.

CUTSCENE_MCP_TOKEN

With --http: the token every request must carry.

Without a key, or when Cutscene does not answer, the free plan applies.

Over HTTP, on your machine

With --http, the same server answers over HTTP on 127.0.0.1 only, at /mcp, for a program of your machine that connects to a server rather than starting one. A web page cannot call it.

• Cutscene is an OAuth 2.1 authorization server. Your assistant introduces itself with the page it publishes on its own site (Client ID Metadata Document), or registers by itself (dynamic client registration), then sends you to Cutscene's “Allow” page.
• After “Allow”, it receives a single-use code, valid for 10 minutes and protected by PKCE (S256), which it exchanges for an access token.
• An access token lasts 60 minutes and is good for the connector's address only: no other page of Cutscene takes it. Your assistant renews it by itself, for 90 days without use at most.
• Each request is handled alone (streamable HTTP, without a session), with the tools that read no file of your computer: pictures and export are done in the editor.

For an MCP client

The discovery documents are at the standard addresses:

• https://app.cutscene.studio/.well-known/oauth-protected-resource/mcp
• https://app.cutscene.studio/.well-known/oauth-authorization-server

The tools available online

It is never ticked in advance, and the server refuses the access without it. Here are its words, as the page shows them:

What your assistant reads (your films, their brand, your pieces, the pictures it looks at) goes to the company that provides it, such as Anthropic for Claude or OpenAI for ChatGPT. If your plan keeps your pictures online, its Cutscene window also shows them, as reduced copies. That window is a page of that company, which can therefore see each picture, through a link valid for ten minutes.

That company may handle all of this outside the European Union, for instance in the United States, without a protection recognised by the European Commission or any safeguard from us. The risks: perhaps no authority to stand up for you, rights harder to enforce, access by that country's authorities.

I agree that what my assistant reads, and the reduced copies of my pictures that its window shows, go to the company that provides it, even outside the European Union, with the risks set out above.

In “My account”, “Connected applications”: “Remove access”, in one click, and the application is refused at once. Changing, setting or removing your password also ends every application's access; your account's keys stay.