*MCP › Connect*

# Connect Make

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

## 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)](https://apps.make.com/c5ZhYquO55e90hoCJ0rzt)

> **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. **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.

## 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 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.

## 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

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](https://docs.filmo.io/mcp/guides/limits-and-context).

## 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](https://docs.filmo.io/mcp/guides/safe-writes#requires-confirmation).

- Transport (Streamable HTTP or SSE): 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/make  
Last updated: 2026-10-25