ZBS Index What actually exists in applied AI, with the source next to it

mcp server

openstreetmap-mcp-server

Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data.

Description as published by the maintainer. Source

  • version 0.3.6
  • active

active — Most recent push to the repository was 2026-08-02.

What this server can do

6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

openstreetmap_lookup_objects(osm_ids, language, extratags)
Fetch address details for one or more known OSM objects by their IDs via Nominatim. Each ID must be prefixed with N (node), W (way), or R (relation), e.g., "N240109189", "W50637691", "R146656". Up to 50 IDs per call. Use when an OSM ID is already known from a prior openstreetmap_query_nearby or openstreetmap_query_bbox result — this is more efficient than a geocoding round trip to get the full Nominatim address record. The results are exactly the objects named in osm_ids: extratags decorates them and cannot select them, and there is no way to ask this tool for objects carrying a given tag. Discover such objects with openstreetmap_query_nearby, openstreetmap_query_bbox, or openstreetmap_query_raw, then pass their IDs here. Required: osm_ids.
openstreetmap_query_bbox(east, west, limit, north, south, offset, amenity, tag_key, tag_value, element_types, timeout_seconds)
Find OSM features within a rectangular geographic area (bounding box) via the Overpass API. Useful for area surveys where you want everything in a region, not proximity searches. Use amenity for common POI types (hospital, pharmacy, cafe, school, etc.) or tag_key + tag_value for other OSM categories (leisure=park, shop=supermarket, natural=peak). Exactly one of amenity or tag_key/tag_value must be provided. Every feature includes its full OSM tag set; the extratags flag (used by the Nominatim-backed openstreetmap_search_places, openstreetmap_reverse_geocode, and openstreetmap_lookup_objects tools) does not apply here. For proximity searches centered on a point, use openstreetmap_query_nearby instead. Required: south, west, north, east.
openstreetmap_query_nearby(lat, lon, limit, offset, amenity, tag_key, tag_value, element_types, radius_meters, timeout_seconds)
Find OSM features within a radius around a geographic point via the Overpass API. The primary tool for "what's near X?" spatial queries. Use amenity for common POI types (hospital, pharmacy, restaurant, cafe, school, atm, etc.) or tag_key + tag_value for other OSM categories (leisure=park, shop=supermarket, natural=peak). Exactly one of amenity or tag_key/tag_value must be provided. Results include all element types specified (nodes cover standalone POIs, ways cover buildings and areas), each with its full OSM tag set, sorted nearest-first by distance_meters from the center point. The extratags flag is not needed here — it applies only to the Nominatim-backed openstreetmap_search_places, openstreetmap_reverse_geocode, and openstreetmap_lookup_objects tools. Required: lat, lon.
openstreetmap_query_raw(limit, query, offset, timeout_seconds)
Execute a raw Overpass QL query for advanced spatial queries that the convenience tools do not cover. Use for multi-type queries, union queries, relation membership, historical queries, or any operation requiring full Overpass QL expressiveness. The query must include [out:json]. Example: "[out:json][timeout:15];node[\"natural\"=\"peak\"](47.5,-122.5,47.7,-122.2);out body;" Returns one page of the result set: use limit and offset to page through it, and read totalFound and truncated to see how much the query matched. Validate complex queries at overpass-turbo.eu before use. For simple "what's near X?" or "what's in this area?" queries, use openstreetmap_query_nearby or openstreetmap_query_bbox instead. Required: query.
openstreetmap_reverse_geocode(lat, lon, zoom, layer, language, extratags)
Convert latitude/longitude coordinates to the nearest address or place name via Nominatim/OpenStreetMap. Returns the closest matching OSM object at the given coordinates. Note: Nominatim finds the nearest indexed OSM object — in dense areas this may differ from the address at the exact coordinate. Use zoom=18 for building-level accuracy, lower zoom values for coarser resolution (e.g., zoom=10 for city-level). The match is made on proximity and layer, never on an OSM attribute tag: extratags decorates the matched object and cannot select one. To find the objects in an area that carry a given tag, use openstreetmap_query_nearby, openstreetmap_query_bbox, or openstreetmap_query_raw. Required: lat, lon.
openstreetmap_search_places(city, layer, limit, query, state, county, street, country, language, extratags, postalcode, featureType, countrycodes, exclude_place_ids)
Convert a place name or address to geographic coordinates and structured place data via Nominatim/OpenStreetMap. Accepts either a free-form query string (e.g., "Space Needle Seattle") or structured address fields (street, city, state, etc.) — the two modes are mutually exclusive. Returns results ordered by Nominatim relevance (importance score). Use countrycodes to restrict results to specific countries. For exhaustive POI lists in an area, use openstreetmap_query_nearby or openstreetmap_query_bbox instead — Nominatim search returns best matches, not all matching objects. Results are matched on name and address relevance, never on an OSM attribute tag: extratags decorates whichever object matched and cannot select one, so a named feature may resolve to a different OSM object than the one carrying the tags you want. To filter or enumerate by tag (surface, sac_scale, ele, access, amenity), use openstreetmap_query_nearby, openstreetmap_query_bbox, or openstreetmap_query_raw.

Last successful function declaration observed on . Source: https://openstreetmap.caseyjhand.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://openstreetmap.caseyjhand.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 4 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-08-02 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 0 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 0.3.6 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-08-02 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License Apache-2.0 Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-08-02 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 6 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe openstreetmap.caseyjhand.com
mcp endpoint status ok The server listed 6 functions when asked. as of probe openstreetmap.caseyjhand.com

Where to get it

Related, by what their authors tagged them

  • io.github.cyanheads/nominatim-mcp-server — last commit 2026-08-02, shares bun, cyanheads, geocoding
    Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data.
  • io.github.gander-tools/osm-tagging-schema-mcp — archived, last commit 2026-05-11, shares openstreetmap, osm
    MCP server for querying and validating OpenStreetMap tags
  • io.github.Acuris-GmbH/acuris-mcp-server — archived, last commit 2026-06-09, shares geocoding, reverse-geocoding
    Address validation, UK postcode lookup (PAF), geocoding & reverse-geocoding in 240+ countries.
  • TrustyData — last commit 2026-07-13, shares geocoding, openstreetmap
    French address quality, geocoding & routing from official data (BAN, INSEE, OpenStreetMap).
  • io.github.GeiserX/pumperly-mcp — last commit 2026-08-01, shares geocoding, openstreetmap
    MCP server for Pumperly — query fuel prices, find stations, and plan routes
  • io.github.geowire/geowire — last commit 2026-07-26, shares geocoding, openstreetmap
    Place search, directions, isochrones & area analysis across 10 map providers. No API key to start.
  • io.github.cyanheads/toolkit-mcp-server — last commit 2026-06-28, shares cyanheads, geolocation
    Generate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics.
  • com.apogeoapi/apogeoapi-mcp — last commit 2026-05-11, shares geolocation
    Geographic data API: 250+ countries, 150K+ cities, IP geolocation, 161 live FX rates.
  • io.github.7mza/geolocation-mcp — last commit 2026-08-05, shares geolocation
    An MCP server that provides fast and up-to-date IP geolocation data.
  • Address Validator API — last commit 2026-07-19, shares geolocation
    Parse, validate and normalize postal addresses. Detect country, verify format. x402.

These share tags the maintainers applied themselves, such as bun, cyanheads, geocoding, geolocation. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

Also from cyanheads

How the author describes it

Topics the maintainer set on GitHub: ai-agent, bun, cyanheads, geocoding, geolocation, mcp, mcp-server, model-context-protocol, nominatim, openstreetmap, osm, overpass, reverse-geocoding, spatial, typescript.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. cyanheads/openstreetmap-mcp-server on GitHub — GitHub, observed , trust tier 3.
  2. Tools declared by the MCP server at https://openstreetmap.caseyjhand.com/mcp — openstreetmap.caseyjhand.com, observed , trust tier 4.
  3. Official MCP Registry — Model Context Protocol, observed , trust tier 1.