*MCP › Connect*

# Connect Claude

> Add Filmo to Claude on the web or the desktop app as a custom connector.

## Before you start

| What | What the vendor documents |
| --- | --- |
| Plan | Custom connectors work on Free (one custom connector), Pro, Max, Team and Enterprise. |
| Who adds the connector | On Team an Owner adds it (Organization settings › Connectors); on Enterprise an Owner or a custom role with “Manage access to Libraries”. On Free, Pro and Max you add it yourself (Customize › Connectors). |
| Who connects | Each member connects with their own Filmo account (Connect on the connector). |
| Administration | A switch beyond the roles above: not documented by the vendor. |

verified on 2026-10-09: [Custom connectors (Claude Help Center)](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) · [Add an unlisted connector](https://claude.com/docs/connectors/custom/add-unlisted) · [Connector authentication](https://claude.com/docs/connectors/building/authentication)

> **Use exactly this URL:** Type `https://app.filmo.io/api/v1/mcp` exactly. Do not use the Filmo domain of your company or any other host: the OAuth metadata names this origin, and a client that compares it with what you typed rejects a different one.

## Connect with OAuth

1. **Open the connectors** Team and Enterprise: an Owner opens Organization settings › Connectors › Add › Custom. Other plans: Customize › Connectors › Add custom connector.
2. **Paste the URL** Name it Filmo and paste `https://app.filmo.io/api/v1/mcp` exactly. Leave the OAuth client options on the default (Claude's published identity, or Register automatically).
3. **Add it, then connect** Each person who will use it opens the connector and chooses Connect. Claude opens Filmo's consent screen.
4. **Consent in Filmo** An administrator of the Filmo account chooses the subscription and the scopes; see “The consent screen” below.

- Claude sends the `scope` of the 401 `WWW-Authenticate` header when it has one, and otherwise asks for every scope in the resource metadata. Filmo's 401 carries the read scopes.
- The `resource` of the protected-resource metadata has to equal the URL as you typed it in Claude, path included.
- The redirect URI of the hosted apps is `https://claude.ai/api/mcp/auth_callback`: it is the host the consent screen shows.
- Claude follows the authorization specifications 2025-03-26, 2025-06-18 and 2025-11-25.
- Scope step-up after a `403 insufficient_scope` on the hosted apps: not documented by the vendor.

## The consent screen

- 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](https://docs.filmo.io/mcp/authentication#before-you-approve).

## Connect with an API key

1. **Use it only if you see it** “Request headers” is a beta feature available to a limited set of organizations; if the section is not in the Add custom connector dialog, use OAuth.
2. **Choose No sign-in** Paste the URL, choose No sign-in as the authentication.
3. **Add the header** Under Request headers add `authorization` with the value `Bearer ` followed by your key. Claude sends the value as written and does not show it again.

- The header is the organization's credential, shared by every member who uses the connector; it cannot be edited later: remove the connector and add it again.

> **Keep the key out of the repository:** Never paste an API key into a file that goes to version control. The examples read it from the environment or ask for it; if one leaks, revoke it and create another.

## Limits of this client

| What | What the vendor documents |
| --- | --- |
| Tools | A limit on the number of tools: not documented by the vendor. |
| Output | A tool result is cut at about 150,000 characters. |
| Time | A tool call times out after 240 seconds. |

## Recommended preset

Rental operations (21): `orders:read`, `orders:write`, `availability:read`, `items:read`, `contacts:read`, `account:read`. It includes the order writes (create, update, archive, reserve, unreserve, cancel and return lines). For read-only work start from a preset marked (read) and add writes by hand only when the assistant needs them.

Every preset and its size are in [Limits and context](https://docs.filmo.io/mcp/guides/limits-and-context).

## What to put on “ask before running”

Customize › Connectors › Filmo: set each tool to Always allow, Needs approval or Blocked.

The tools that must ask for approval are in [Safe writes](https://docs.filmo.io/mcp/guides/safe-writes#requires-confirmation).

- Claude documents `readOnlyHint` and `destructiveHint` as hints it and its users read; how each one changes approval on claude.ai is not documented.
- Support for `_meta["anthropic/requiresUserInteraction"]` on claude.ai and the desktop app: not documented by the vendor.

## Check the connection

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

---

Canonical URL: https://docs.filmo.io/mcp/connect/claude  
Last updated: 2026-10-25