where_was_it_filmed — filming locations MCP Tool
where_was_it_filmed
(where was it filmed) is one of 8 tools on the
filming locations
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call where_was_it_filmed from your client
- Claude Code filming locations where_was_it_filmed run in your project directory
- Claude Desktop filming locations where_was_it_filmed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor filming locations where_was_it_filmed ~/.cursor/mcp.json
- VS Code filming locations where_was_it_filmed .vscode/mcp.json
- Zed filming locations where_was_it_filmed ~/.config/zed/settings.json
- Windsurf filming locations where_was_it_filmed ~/.codeium/windsurf/mcp_config.json
- Cline filming locations where_was_it_filmed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI filming locations where_was_it_filmed ~/.gemini/settings.json
- Grok filming locations where_was_it_filmed .mcp.json (in your project root)
- ChatGPT filming locations where_was_it_filmed Settings → Connectors → Advanced → Developer mode
- Claude.ai filming locations where_was_it_filmed Settings → Connectors → Add custom connector
- LangChain filming locations where_was_it_filmed pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http filming-locations https://thefilmmap.com/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.