Connect Claude Code

verified on 2026-10-09: Connect Claude Code to MCP servers · Permissions

1. 1

   Add the server

   Run the command below.

2. 2

   Authenticate

   In a session run /mcp, choose filmo and authenticate; or run claude mcp login filmo in a shell.

3. 3

   Consent in Filmo

   An administrator chooses the subscription and the scopes in Filmo's consent screen; see below.

• When oauth.scopes is not set, Claude Code requests the scope of the 401 WWW-Authenticate header or of the resource metadata, and sends none when neither has one. Filmo's 401 carries the read scopes.
• On a 403 insufficient_scope it fails with “needs additional permissions”; there is no automatic step-up. Add the scope to oauth.scopes and authenticate again.
• It uses a loopback redirect (http://localhost:<port>/callback); --callback-port fixes the port.

• Only the *:read scopes the client asked for are checked (every read scope when it asks for none).
• Write scopes, workflows:run and ai:ask always start unchecked, even if the client asks for them; the ones it asked for carry the label “Requested by the integration”.
• Check by hand only what the assistant needs, and leave ai:ask unchecked unless you want it to spend AI credits.

To change the scopes later, remove the connector and add it again.

Before you approve, read Authentication.

1. 1

   Put the key in your environment

   Export FILMO_API_KEY from your shell profile or a secrets manager. Use that exact name or one of your own: the credential-like names Claude Code reserves (such as ANTHROPIC_API_KEY or NPM_TOKEN) read as empty in remote headers.

2. 2

   Add the server in the user scope

   The command below stores the entry in your user configuration, outside any repository.

3. 3

   Or share a project file without the key

   In .mcp.json the header carries ${FILMO_API_KEY}, never the value, so the file is safe to commit.

claude mcp add --transport http filmo --scope user https://app.filmo.io/api/v1/mcp \
  --header "Authorization: Bearer $FILMO_API_KEY"

{
  "mcpServers": {
    "filmo": {
      "type": "http",
      "url": "https://app.filmo.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${FILMO_API_KEY}"
      }
    }
  }
}

• Never use --scope project with a literal key: that scope writes .mcp.json, which Claude Code's documentation suggests checking into version control.

Rental operations (21): orders:read, orders:write, availability:read, items:read, contacts:read, account:read. Claude Code defers tool definitions, so the preset is about what the key may do, not about context. It includes the order writes, cancelling included; for read-only work pick a preset marked (read).

Every preset and its size are in Limits and context.

Permission rules mcp__filmo (the whole server) or mcp__filmo__<tool>. A tool with _meta["anthropic/requiresUserInteraction"]: true asks on every call, in every mode, with no “don't ask again”.

The tools that must ask for approval are in Safe writes.

• Claude Code does not auto-approve by readOnlyHint or destructiveHint: it is not in its documentation.

Ask the assistant: “Which Filmo account am I connected to?” It should call filmo_account_get, a read tool that returns no personal data.