FilmMap MCP server
Related Servers
Alternatives to FilmMap MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides location-based services and geospatial data from OpenStreetMap, enabling geocoding, route directions, nearby place search, and neighborhood analysis through natural language.12MIT
- AlicenseAqualityDmaintenanceEnhances LLM capabilities with location-based services and geospatial data, enabling users to geocode addresses, find nearby points of interest, get directions, optimize meeting points, and analyze neighborhoods.12226MIT
- AlicenseAqualityBmaintenanceLets LLMs rank, compare, and connect actors and movies from local IMDb non-commercial datasets stored in DuckDB, with Wikidata enrichment.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to search movies and actor profiles, discover soundtracks, and generate curated Spotify playlists, with full playback control and playlist management through natural language.1MIT
- AlicenseAqualityAmaintenanceEnables screenwriters to search for similar scenes, fetch scene details, list indexed movies, find mood reference scenes, and get analysis style guidance, all grounded in real produced scripts.5MIT
- AlicenseBqualityCmaintenanceEnables movie and TV recommendation workflows, including title resolution, evidence tracking, candidate retrieval from MovieLens and TMDB, and recording of recommendation runs and reactions.8MIT
TDQS
Scored across 8 tools
Each tool answers a clearly distinct question: title-to-places, place-to-titles, name search, ranked lists, statistics, and proximity. Even the two question-shaped tools are unambiguous because one takes a production and the other takes a place.
Naming mixes verb-led tools like search_productions and list_countries with question-style names like where_was_it_filmed and noun phrases like top_locations and locations_near. All names are readable and lowercased, but there is no single consistent convention across the set.
Eight tools is well within the ideal range for a read-only atlas, and each tool covers a distinct workflow: lookup, search, ranking, statistics, and spatial queries. None feels redundant or extraneous.
The surface covers the core bidirectional lookup (production-to-locations and location-to-productions), title disambiguation, location search, country/global rankings, statistics, and nearby searches. For a read-only Wikidata-backed atlas there are no obvious dead ends or missing core operations.