Connect
Connect Make
Call Filmo tools from a Make scenario with the MCP Client app.
Before you start
Link to this section: Before you start| What | What the vendor documents |
|---|---|
| Plan | The MCP Client app is in open beta for all users; the page states no plan restriction. |
| Who adds the connector | Whoever builds the scenario creates the connection. |
| Who connects | Whoever creates the connection; with OAuth, a Filmo administrator consents. |
| Administration | Organization settings for the app: not documented by the vendor. |
verified on 2026-10-09: MCP Client app (Make)
Use exactly this URL
Type https:// 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
Link to this section: Connect with OAuthAdd a module
Add the MCP Client module (Call a tool, or Execute an action with AI) to a scenario and choose Create a connection.
Enter the server
Choose + New MCP Server and type
https://.app. filmo. io /api /v1 /mcp Allow Make's redirect
Make's redirect URI is
https://. Filmo registers the client dynamically, so there is nothing to add on Filmo's side.www. make. com /oauth /cb /mcp 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.
The consent screen
Link to this section: The consent screen- Only the
*:readscopes the client asked for are checked (every read scope when it asks for none). - Write scopes,
workflows:runandai:askalways 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:askunchecked 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.
Connect with an API key
Link to this section: Connect with an API keyUse 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.
Test with a read tool
Make does not document which header it sends the value in. Check the connection with
filmo_account_getbefore 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.
Limits of this client
Link to this section: 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 output limit: not documented by the vendor. |
Recommended preset
Link to this section: Recommended presetAvailability 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.
What to put on “ask before running”
Link to this section: What to put on “ask before running”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.
Check the connection
Link to this section: Check the connectionAsk the assistant: “Which Filmo account am I connected to?” It should call filmo_account_get, a read tool that returns no personal data.
Related pages
Link to this section: Related pagesIntroduction
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?