# mcp.film client setup profiles

Generated: 2026-06-29T08:03:10.402Z

Machine JSON: https://mcp.film/api/client-profiles.json

## Clients

### Claude Code (`claude_code`)
- Works with remote URLs: yes
- Works with local stdio: yes
- Config surface: CLI command
- Best for: Local coding agents that can run commands and connect hosted Streamable HTTP MCP servers.
- Install strategy: Prefer install.claude_code when present; otherwise use install.remote_url with --transport http or install.stdio_command after required env vars are set.
- Example: `claude mcp add --transport http --scope user martini https://www.martini.film/mcp`
### Claude Desktop (`claude_desktop`)
- Works with remote URLs: yes
- Works with local stdio: yes
- Config surface: claude_desktop_config.json
- Best for: Local desktop sessions that can spawn stdio servers or bridge hosted remotes through mcp-remote.
- Install strategy: Use the generated JSON on each listing; remote servers are represented with npx mcp-remote, local servers with command/args/env.
- Example: `{"mcpServers":{"martini":{"command":"npx","args":["-y","mcp-remote","https://www.martini.film/mcp"]}}}`
### Cursor (`cursor`)
- Works with remote URLs: yes
- Works with local stdio: yes
- Config surface: .cursor/mcp.json
- Best for: Coding-agent workspaces that need project-local MCP configuration.
- Install strategy: Use the generated Cursor JSON on each listing; hosted servers use a url field, local servers use command/args/env.
- Example: `{"mcpServers":{"martini":{"url":"https://www.martini.film/mcp"}}}`
### Hosted remote MCP clients (`hosted_remote`)
- Works with remote URLs: yes
- Works with local stdio: no
- Config surface: Client connector UI or remote MCP URL field
- Best for: ChatGPT, Claude web, Gemini-style hosted clients, and automations that cannot spawn local stdio processes.
- Install strategy: Use only entries with install.remote_url, complete the vendor OAuth/API-key flow, and avoid local-only servers unless the client provides a trusted bridge.
- Example: `https://www.martini.film/mcp`
### mcp-film meta-MCP (`meta_mcp`)
- Works with remote URLs: no
- Works with local stdio: yes
- Config surface: stdio package
- Best for: Agents that want to search, route briefs, plan stacks, and fetch install configs from mcp.film as tools.
- Install strategy: Connect the directory itself, then call search_film_mcps, recommend_film_mcps, plan_film_stack, and get_install_config.
- Example: `claude mcp add mcp-film -- npx -y mcp-film`
## Martini fast start

```sh
claude mcp add --transport http --scope user martini https://www.martini.film/mcp
```

Remote endpoint: `https://www.martini.film/mcp`

## Starter examples

- [Martini](https://mcp.film/mcps/martini.md): remote; auth oauth
- [Runway MCP](https://mcp.film/mcps/runway.md): remote; auth oauth
- [fal MCP Server](https://mcp.film/mcps/fal.md): remote; auth api_key (FAL_KEY)
- [Canva MCP](https://mcp.film/mcps/canva.md): remote; auth oauth
- [Airtable MCP Server](https://mcp.film/mcps/airtable.md): remote; auth oauth
- [Palmier Pro](https://mcp.film/mcps/palmier-pro.md): local; auth local-app
- [Blender MCP](https://mcp.film/mcps/blender.md): local; auth local-app

Rule: hosted web clients should use entries with install.remote_url. Local stdio packages need a client that can spawn local processes or a trusted bridge.