Connect other clients

verified on 2026-10-09: mcp-remote · MCP Inspector · Zapier MCP Client · Raycast MCP · GitHub Copilot coding agent

1. 1

   Point the client at the URL

   https://app.filmo.io/api/v1/mcp, Streamable HTTP.

2. 2

   Use OAuth where the client has it

   Zapier (answer Yes to “Does the server use OAuth?”), Raycast (Dynamic) and MCP Inspector register dynamically. The coding agent of GitHub Copilot does not support OAuth for remote servers.

• 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. 1

   Zapier with a key

   If you use a key instead of OAuth, choose Streamable HTTP and paste a key made for it in the Bearer Token field.

2. 2

   Raycast

   Choose the HTTP type, enter the URL and add an Authorization header in HTTP Headers. Raycast stores it in the app, not in a repository.

3. 3

   GitHub Copilot coding agent

   Reference a repository secret named COPILOT_MCP_FILMO_KEY in the header; GitHub requires the names to start with COPILOT_MCP_. Whether a variable is interpolated inside a longer header value is not documented: test it.

4. 4

   Clients that only speak stdio

   Run mcp-remote with the header taken from an environment variable (below).

5. 5

   MCP Inspector

   Pass the header from your environment; Inspector saves headers in mcp.json exactly as written, so use the command line and do not save the configuration.

{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://app.filmo.io/api/v1/mcp",
    "--header",
    "Authorization:${FILMO_AUTH}"
  ],
  "env": {
    "FILMO_AUTH": "Bearer ${FILMO_API_KEY}"
  }
}

npx @modelcontextprotocol/inspector --cli https://app.filmo.io/api/v1/mcp --transport http \
  --header "Authorization: Bearer $FILMO_API_KEY" --method tools/list

{
  "mcpServers": {
    "filmo": {
      "type": "http",
      "url": "https://app.filmo.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer $COPILOT_MCP_FILMO_KEY"
      },
      "tools": [
        "filmo_account_get"
      ]
    }
  }
}

• mcp-remote fills ${VAR} from the env block of the configuration, and its Authorization:${VAR} form (no space) avoids a bug with spaces in arguments on some clients.
• MCP Inspector requires Node 22.19.0 or newer; a tools/call that returns isError: true still prints the result but exits with code 5.
• GitHub Copilot's coding agent requires tools on each server and uses tools without asking.
• Obsidian has no official MCP client documentation; community plugins are not supported by Filmo.

Availability and schedule (read) (20): availability:read, schedule:read, planner:read, staff:read, vehicles:read, items:read, spaces:read, kits:read, account:read. Start narrow: these clients rarely ask before running a tool.

Every preset and its size are in Limits and context.

GitHub Copilot's coding agent and automation tools run tools without asking: restrict tools and the key's scopes.

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

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