Connect Cursor

verified on 2026-10-09: MCP in Cursor · Install links

1. 1

   Add the server without headers

   Put an entry with only url in ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor runs the OAuth flow for servers that need it.

2. 2

   Authenticate

   Sign in when Cursor asks, and consent in Filmo.

• auth.scopes pins scopes; without it Cursor discovers scopes_supported from the authorization server metadata.
• What Cursor does with the scope of a 401 challenge: not documented by the vendor.

• 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

   Export the key

   Set FILMO_API_KEY in the environment Cursor starts from.

2. 2

   Reference it

   Cursor resolves ${env:NAME} in url and headers, so the file holds no value. Prefer ~/.cursor/mcp.json, which is not part of any repository.

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

The link installs the OAuth entry (no key in it). Cursor builds it from the server configuration, base64-encoded.

cursor://anysphere.cursor-deeplink/mcp/install?name=filmo&config=eyJ1cmwiOiJodHRwczovL2FwcC5maWxtby5pby9hcGkvdjEvbWNwIn0=

Availability and schedule (read) (20): availability:read, schedule:read, planner:read, staff:read, vehicles:read, items:read, spaces:read, kits:read, account:read. About 40 tools is the soft ceiling: pick a preset of 20 to 30.

Every preset and its size are in Limits and context.

Cursor asks for approval before using MCP tools by default; admins can allowlist tools to auto-run.

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

• Any use of readOnlyHint or destructiveHint for approval: not documented by the vendor.

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