*MCP › Connect*

# Connect other clients

> Zapier, Raycast, GitHub Copilot, Obsidian, MCP Inspector and any client that speaks MCP over HTTP.

## Before you start

| What | What the vendor documents |
| --- | --- |
| Plan | Zapier MCP Client is a beta feature. Raycast marks MCP over HTTP “Pro Exclusive”. |
| Who adds the connector | The person who configures the client. |
| Who connects | The same person, with a key or OAuth. |
| Administration | GitHub Copilot's coding agent: repository Settings › Copilot › MCP servers. |

verified on 2026-10-09: [mcp-remote](https://github.com/geelen/mcp-remote) · [MCP Inspector](https://modelcontextprotocol.io/docs/2026-07-28/tools/inspector.md) · [Zapier MCP Client](https://help.zapier.com/hc/en-us/articles/38777069364109) · [Raycast MCP](https://manual.raycast.com/ai/model-context-protocol) · [GitHub Copilot coding agent](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/extend-coding-agent-with-mcp)

> **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. **Point the client at the URL** `https://app.filmo.io/api/v1/mcp`, Streamable HTTP.
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.

## 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. **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. **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. **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. **Clients that only speak stdio** Run `mcp-remote` with the header taken from an environment variable (below).
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.

**mcp-remote**

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

**MCP Inspector**

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

**GitHub Copilot**

```json
{
  "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.

> **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`. Start narrow: these clients rarely ask before running a tool.

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”

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

## 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/other-clients  
Last updated: 2026-10-25