Connect

Connect Windsurf

Add Filmo to Windsurf's Cascade with an API key read from your environment.

WhatWhat the vendor documents
PlanPlans: not documented by the vendor.
Who adds the connectorYou, in mcp_config.json. Team and Enterprise admins can switch MCP off and allowlist servers by name.
Who connectsEach user, with their own configuration file.
AdministrationOnce one server is allowlisted, every server that is not is blocked; the id has to match the key in mcp_config.json.

verified on 2026-10-09: MCP in Cascade

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.

  1. Add the server

    Add an entry with only serverUrl to mcp_config.json.

  2. Authenticate

    Windsurf documents OAuth support for each transport; the steps of its dialog are not documented, so follow what the client shows and consent in Filmo.

  • How scopes are chosen and whether tools are listed again after sign-in: 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. Open the file

    In the Cascade panel open the Actions menu and choose the MCP configuration file.

  2. Reference the key

    ${env:NAME} is filled from the environment in serverUrl, url and headers; an unset variable becomes an empty string.

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

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.

WhatWhat the vendor documents
ToolsCascade has a limit of 100 total tools it can access at any time, across servers.
OutputA tool output limit: not documented by the vendor.

Availability and schedule (read) (20): availability:read, schedule:read, planner:read, staff:read, vehicles:read, items:read, spaces:read, kits:read, account:read. Keep the total under 100 with your other servers.

Every preset and its size are in Limits and context.

Switch a server on or off in the MCPs section; disable single tools with disabledTools in the server entry.

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

  • The page describes the configuration of the legacy Cascade agent; its documentation now lives with Devin Desktop.

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

  • Introduction

    MCP quickstart

    Connect one assistant, check it with a read tool and choose the scopes it needs.

  • Access

    Authentication and permissions

    Authenticate with an API key in a header, or let the client sign in with OAuth 2.1. Either way the scopes decide which tools exist.

  • Guides

    Safe writes

    An assistant that can write can also write the wrong thing. Decide which tools need a person, retry without duplicating, and know what a write sets in motion.

Was this page helpful?