FilmMap MCP server

FilmMap MCP server

Enables natural-language queries about real filming locations and the productions recorded at them, including search, proximity, and ranking tools.

Category
Visit Server

README

FilmMap MCP server

A Model Context Protocol server for the FilmMap atlas: 15,272 real filming locations across 161 countries, joined to the 12,762 films, series, video games, anime and manga recorded at them, with coordinates, fame ranking, per-place production lists and the source behind every claim.

It is already running. Point a client at the hosted endpoint — there is no install, no signup and no API key:

https://thefilmmap.com/mcp

Streamable HTTP, stateless, POST-only (a GET returning 405 is correct).

Client configuration

{
  "mcpServers": {
    "filmmap": {
      "type": "http",
      "url": "https://thefilmmap.com/mcp"
    }
  }
}

Tools

Tool What it does
where_was_it_filmed Give a title, get the places it was shot at, each with its evidence
what_was_filmed_here The inverse, and the question this atlas is unusual for answering: give a place, get everything recorded as made there
search_productions Find productions by name, accent- and case-insensitive, best match first
search_locations Find places by name, filterable by country or kind of place
locations_near Places within a radius of a WGS84 coordinate, each with distance_km
top_locations The atlas ranked, worldwide or inside one country or one kind of place
list_countries Every country with how many filming locations it holds
get_statistics Live aggregates — totals by medium and by kind of place, top countries, busiest places

What an answer will and will not claim

This is the part worth reading before wiring it into anything that writes prose.

Films and series are placed by filming location (P915). Video games, anime and manga are filmed nowhere, so they are placed by narrative location (P840) — where the story is set — and every record says which relation it carries. Repeating one as the other publishes a false claim.

A place is not a scene. P915 records that a production filmed at a place and stops there. Which scene was shot where is not in the data and must not be inferred from it.

Two kinds of evidence, never merged. Most links are Wikidata statements. Some are places named in a production's English Wikipedia Filming section, or a setting category its editors filed it under; those arrive in their own fields, labelled with the exact article and section they were read from. Say "per Wikipedia" when you repeat one.

Coverage is uneven and the server says so. 834 productions are recorded only at country level and appear with countries and no coordinates. A further 3,906 cannot be placed at all; they are published as a work list at thefilmmap.com/gaps/ so they can be fixed on Wikidata.

Data

Built from Wikidata, with photographs from Wikimedia Commons and article text linked rather than bundled. The factual records are CC0 and downloadable as GeoJSON and CSV from thefilmmap.com/data, also mirrored on GitHub.

The server reads one file, atlas-compact.json, which is the site's own wire format and is rebuilt on every deploy.

Running it yourself

ATLAS_JSON=/path/to/atlas-compact.json PORT=8896 node server.mjs

Or with Docker, which bakes the public copy of the atlas into the image:

docker build -t filmmap-mcp .
docker run -p 8896:8896 filmmap-mcp     # → http://localhost:8896/mcp

HOST defaults to 127.0.0.1; the container sets 0.0.0.0 because the default is unreachable from outside a container.

Licence

MIT for the server. The dataset it serves is CC0; photographs and Wikipedia text referenced by URL stay under their own licences.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured