Connect

Connect Make

Call Filmo tools from a Make scenario with the MCP Client app.

WhatWhat the vendor documents
PlanThe MCP Client app is in open beta for all users; the page states no plan restriction.
Who adds the connectorWhoever builds the scenario creates the connection.
Who connectsWhoever creates the connection; with OAuth, a Filmo administrator consents.
AdministrationOrganization settings for the app: not documented by the vendor.

verified on 2026-10-09: MCP Client app (Make)

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 a module

    Add the MCP Client module (Call a tool, or Execute an action with AI) to a scenario and choose Create a connection.

  2. Enter the server

    Choose + New MCP Server and type https://app.filmo.io/api/v1/mcp.

  3. Allow Make's redirect

    Make's redirect URI is https://www.make.com/oauth/cb/mcp. Filmo registers the client dynamically, so there is nothing to add on Filmo's side.

  4. Consent in Filmo

    An administrator chooses the subscription and the scopes. Choose only what the scenario needs.

  • Make documents one redirect URI on www.make.com; it lists none per zone.
  • 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. Use the key field

    For a server you enter by hand, Make has an API Key / Access token field. Paste a key made for this scenario, with only the scopes it needs.

  2. Test with a read tool

    Make does not document which header it sends the value in. Check the connection with filmo_account_get before building on it.

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
ToolsA limit on the number of tools: not documented by the vendor.
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. A scenario runs without a person looking: start from a read preset and add writes only for the steps that need them.

Every preset and its size are in Limits and context.

A scenario runs tools without asking. The only guard is the key's scopes, so give it read scopes unless the scenario writes.

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

  • Transport (Streamable HTTP or SSE): 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.

  • 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?