get_film_playbook — mcp.film directory MCP Tool Read-only
get_film_playbook
(get film playbook) is one of 15 tools on the
mcp.film directory
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_film_playbook from your client
- Claude Code mcp.film directory get_film_playbook run in your project directory
- Claude Desktop mcp.film directory get_film_playbook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp.film directory get_film_playbook ~/.cursor/mcp.json
- VS Code mcp.film directory get_film_playbook .vscode/mcp.json
- Zed mcp.film directory get_film_playbook ~/.config/zed/settings.json
- Windsurf mcp.film directory get_film_playbook ~/.codeium/windsurf/mcp_config.json
- Cline mcp.film directory get_film_playbook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp.film directory get_film_playbook ~/.gemini/settings.json
- Grok mcp.film directory get_film_playbook .mcp.json (in your project root)
- ChatGPT mcp.film directory get_film_playbook Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp.film directory get_film_playbook Settings → Connectors → Add custom connector
- LangChain mcp.film directory get_film_playbook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http directory https://mcp.film/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.