Guides
For administrators
An assistant acts with the consent of one of your administrators. Decide who may connect, what they may grant and how to take it back.
Who can use Filmo from which client
Link to this section: Who can use Filmo from which clientTwo different people are involved. The client's own administrator decides who may add a connector; a Filmo administrator consents to what the connection can do. Only administrators of the Filmo account can consent.
| Client | Plan | Who adds the connector | Who connects | Administration | Verified on |
|---|---|---|---|---|---|
| Claude | Custom connectors work on Free (one custom connector), Pro, Max, Team and Enterprise. | On Team an Owner adds it (Organization settings › Connectors); on Enterprise an Owner or a custom role with “Manage access to Libraries”. On Free, Pro and Max you add it yourself (Customize › Connectors). | Each member connects with their own Filmo account (Connect on the connector). | A switch beyond the roles above: not documented by the vendor. | 2026-10-09 |
| Claude Code | No plan restriction is stated for servers you add yourself. | You, with claude mcp add. On Team and Enterprise, only admins add connectors at claude.ai/customize/connectors; managed settings can allow or deny servers. | You authenticate with /mcp (OAuth) or send your own key. | Managed settings: allowedMcpServers, deniedMcpServers, managed-mcp.. | 2026-10-09 |
| ChatGPT | Set by OpenAI and it changes: see OpenAI's article on developer mode and MCP apps. | Account and workspace policies of ChatGPT apply to adding a custom MCP server; OpenAI's article says who may enable developer mode. | Whoever uses the connector authorizes it with OAuth; a Filmo administrator consents. | Workspace policies and, for Business and Enterprise, the roles in OpenAI's article. | 2026-10-09 |
| Cursor | No plan requirement is stated on the MCP page. | You, in mcp.. Teams approve servers in Dashboard › Plugins & MCPs; admins can restrict remote URLs to patterns. | Each user authenticates in the client. | URL allowlist, tool allowlists for auto-run, and a network denylist. | 2026-10-09 |
| VS Code | Which Copilot plans can use MCP servers in VS Code: not documented by the vendor. | You, with MCP: Add Server. In Copilot Business and Enterprise an organization policy (“MCP servers in Copilot”, off by default) governs access. | Each user authenticates in VS Code. | VS Code policies: chat., allow and deny lists, managed servers only. | 2026-10-09 |
| Windsurf | Plans: not documented by the vendor. | You, in mcp_config.. Team and Enterprise admins can switch MCP off and allowlist servers by name. | Each user, with their own configuration file. | Once one server is allowlisted, every server that is not is blocked; the id has to match the key in mcp_config.. | 2026-10-09 |
| OpenAI Codex | Plans: not documented by the vendor. | You, with codex mcp add or config.. Workspace admins can restrict servers with managed requirements. | codex mcp login filmo for OAuth. | The enterprise mcp_servers requirement. | 2026-10-09 |
| Gemini CLI | Plans: not documented by the vendor. | You, with gemini mcp add or settings.. Admins can restrict servers with mcp. in the system settings file. | /mcp auth filmo for OAuth (it needs a browser: not on a headless machine). | mcp. and includeTools in the system settings. | 2026-10-09 |
| Make | The MCP Client app is in open beta for all users; the page states no plan restriction. | Whoever builds the scenario creates the connection. | Whoever creates the connection; with OAuth, a Filmo administrator consents. | Organization settings for the app: not documented by the vendor. | 2026-10-09 |
| n8n | Plans: not documented by the vendor. | Whoever builds the workflow adds the node and its credential. | Whoever creates the credential; with OAuth, a Filmo administrator consents. | Self-hosted: the base URL of the instance sets the redirect URI. | 2026-10-09 |
| Other clients | Zapier MCP Client is a beta feature. Raycast marks MCP over HTTP “Pro Exclusive”. | The person who configures the client. | The same person, with a key or OAuth. | GitHub Copilot's coding agent: repository Settings › Copilot › MCP servers. | 2026-10-09 |
What the consent screen checks by default
Link to this section: What the consent screen checks by default- Only the
*:readscopes the client asked for are checked. If it asked for none, every read scope is checked. - Write scopes,
workflows:runandai:askstart unchecked, even when the client asks for them. The ones it asked for carry the label “Requested by the integration”; the ones it did not ask for carry “Not requested by the integration”. - You choose the subscription the connection is bound to. You can grant a scope the client did not ask for.
- The screen shows the host the client redirects to and warns when every redirect of the client is on this computer (loopback).
Leave `ai:ask` unchecked
It spends the account's AI credits and can search the web. No preset includes it. Check it only for an assistant that must ask Filmo's AI and that you trust with that budget.
Before you approve
Link to this section: Before you approveThe same checklist as Authentication: the registration of clients is open, so anyone can register a client under any name. Check the host, do not approve a consent you did not start and distrust clients that only redirect to your own computer.
Whose changes are they
Link to this section: Whose changes are theyWhat an assistant writes is attributed to the administrator who consented, under the connection's name. If that person stops being an administrator, the connection stops working.
Revoking
Link to this section: Revoking- Revoke a connection or a key in the API and MCP page of the app's settings. The access token stops working at once and the refresh token can no longer be exchanged, so the client must ask for consent again.
- Connections count toward the limit of 50 keys that are not revoked per subscription (expired keys count too).
- Remove the connector in the client too, so it does not keep asking.
Data protection and prompt injection
Link to this section: Data protection and prompt injectionEverything an assistant reads goes to the model of its client, and text written by customers can carry instructions. Grant the narrowest scopes and keep the confirmation list on: Safe writes.
Automations
Link to this section: AutomationsMost writes by an assistant can start the account's event workflows like a change made in the app, and they can notify customers. Review the active workflows before granting write scopes.
Related pages
Link to this section: Related pagesAccess
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?