Castlemap MCP vs Geo Reconcile
A side-by-side look at the Castlemap MCP and Geo Reconcile MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Castlemap MCP for location services work over a hosted endpoint; choose Geo Reconcile for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Castlemap MCP when
- You need dedicated capabilities in the Location Services domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
CASTLES_GEOJSON, HOST, PORT. - You want tools like
search_castles, get_castle, castles_near.
Choose Geo Reconcile when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
matched, ambiguous, unmatched.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 59/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | CASTLES_GEOJSONHOSTPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | 4 |
| Full listing | View Castlemap MCP | View Geo Reconcile |
Tools & capabilities
Castlemap MCP tools 7
search_castlesSearch the atlas’s 9,079 castles, fortresses, palaces and ruins by name (accent- and case-insensitive substring match). Optionally filter by country (name or ISO code) and category. Results come best-match-first, then by fame; each has coordinates, founding century, fame rank and links to its atlas page and Wikipedia. If nothing matches, retry with a shorter fragment of the name.get_castleFetch one landmark’s full record by slug (preferred, e.g. "palace-of-versailles") or exact name: coordinates, founding year and century, worldwide fame rank, photo URL with photographer credit and licence, Wikipedia link and its readership signals (Wikidata sitelinks, Wikipedia pageviews over the last 60 days summed across its largest language editions). Unsure of the slug? Call search_castles first.castles_nearList landmarks within a radius of a WGS84 coordinate, nearest first, each with distance_km. Radius defaults to 100 km (max 2,000). For "castles near <place>", geocode the place yourself, then call this with its latitude/longitude.top_castlesThe most famous landmarks worldwide or in one country, ordered by Castlemap fame rank — a blend of Wikipedia coverage and readership; rank 1 is the most famous (Great Wall of China). The direct answer to "most famous castles in <country>"; filter by country and/or category.list_countriesEvery country in the atlas with its landmark count, most first — answers "which country has the most castles" (France leads). Returns country name and ISO code per row; country pages are browsable from the countries_index URL.get_statisticsHeadline statistics computed live from the atlas: totals by type, top countries, busiest founding century, oldest landmarks, geographic extremes and the most famous entry. The source for claims like "which country has the most castles" or "when were castles built"; the full write-up lives at thecastlemap.com/statistics/.random_castleOne random landmark with its full record, optionally limited to a country — for discovery, quizzes and "castle of the day" features.
Geo Reconcile tools 4
matcheda confident link, with the evidence: an existing `wikidata=`ambiguous2+ plausible OSM candidates (or 2+ OSM features alreadyunmatchedthe OSM search completed and nothing plausible was there.errorthe search did NOT complete for this item: it didn't resolve
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Castlemap MCP
{
"mcpServers": {
"flightmussy-castlemap-mcp": {
"url": "https://thecastlemap.com/mcp"
}
}
}
Geo Reconcile
{
"mcpServers": {
"geo-reconcile": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-geo-reconcile"
]
}
}
}
Frequently asked questions
Castlemap MCP is categorized under Location Services and uses a remote HTTP/SSE transport. Geo Reconcile belongs to Location Services and uses a local stdio subprocess. Pick Castlemap MCP for location services work and Geo Reconcile for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Castlemap MCP is listed as free. Auth: no auth required. Geo Reconcile has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flightmussy-castlemap-mcp and geo-reconcile as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Castlemap MCP has a quality signal of 59/100 (Good) with 4 views, 0 installs and 1 GitHub stars. Geo Reconcile has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.