ch.overpass/overpassv1.0.1 Domain verified
Overpass API on the full planet with history, plus geocoding and elevation. Needs an API key.
Maintained by@cdutsov(verified)Also a maintainer?
Try it
Call this server's tools from your browser. Nothing to install.
https://api.overpass.ch/v1/mcp
API key from https://overpass.ch/dashboard/keys
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
account_status Read-only
The plan of the API key of this connection and its use this month: Overpass requests used and left, when the allowance starts again, running queries, elevation lookups, geocoding requests, and the date of the data. It does not count as a request.
This tool takes no arguments.
Install
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
One click: Add to Cursor Add to VS Code Add to LM StudioThen replace the YOUR_ values and {placeholders} with your own.
Run in a terminal
claude mcp add --transport http overpass https://api.overpass.ch/v1/mcp \ --header 'X-API-Key: YOUR_X_API_KEY'
Headers
X-API-Key(required): API key from https://overpass.ch/dashboard/keys
Tools (7)
Tool list last changed Nov 4, 2026.
account_statusThe plan of the API key of this connection and its use this month: Overpass requests used and left, when the allowance starts again, running queries, elevation lookups, geocoding requests, and the date of the data. It does not count as a request.
read-only
account_status
The plan of the API key of this connection and its use this month: Overpass requests used and left, when the allowance starts again, running queries, elevation lookups, geocoding requests, and the date of the data. It does not count as a request.
No arguments.
Input schema (JSON)
{
"type": "object",
"properties": {},
"additionalProperties": false
}elevation_pointsHeights above sea level in metres for a list of points, negative at sea. Switzerland and Liechtenstein: swissALTI3D, a 2 m grid of the ground (credit "© swisstopo"). Elsewhere on land: Copernicus GLO-30, a 30 m grid of the surface that includes buildings and trees. At sea: GEBCO. Each point counts as one lookup; account_status shows the plan maximum per call.
read-only
elevation_points
Heights above sea level in metres for a list of points, negative at sea. Switzerland and Liechtenstein: swissALTI3D, a 2 m grid of the ground (credit "© swisstopo"). Elsewhere on land: Copernicus GLO-30, a 30 m grid of the surface that includes buildings and trees. At sea: GEBCO. Each point counts as one lookup; account_status shows the plan maximum per call.
| Argument | Type | Description |
|---|---|---|
| points* | array | the points, each with lat and lon |
| max_chars | integer | most characters of the answer to show; larger answers are cut, and offset shows the next part |
Input schema (JSON)
{
"type": "object",
"required": [
"points"
],
"properties": {
"points": {
"type": "array",
"items": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "latitude, -90 to 90"
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "longitude, -180 to 180"
}
},
"additionalProperties": false
},
"minItems": 1,
"description": "the points, each with lat and lon"
},
"max_chars": {
"type": "integer",
"default": 30000,
"maximum": 200000,
"minimum": 2000,
"description": "most characters of the answer to show; larger answers are cut, and offset shows the next part"
}
},
"additionalProperties": false
}elevation_profileElevation profile along a path of two or more points: distance, ascent, descent, the lowest and the highest point, and up to 100 points along the way (distance from the start, height, lat, lon). The path is sampled every 90 m unless samples or interval_m is set. Each sample counts as one lookup, up to the plan maximum per call.
read-only
elevation_profile
Elevation profile along a path of two or more points: distance, ascent, descent, the lowest and the highest point, and up to 100 points along the way (distance from the start, height, lat, lon). The path is sampled every 90 m unless samples or interval_m is set. Each sample counts as one lookup, up to the plan maximum per call.
| Argument | Type | Description |
|---|---|---|
| path* | array | the points of the path in order, each with lat and lon |
| samples | integer | number of samples along the path |
| interval_m | number | metres between samples, at least 10 |
Input schema (JSON)
{
"type": "object",
"required": [
"path"
],
"properties": {
"path": {
"type": "array",
"items": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "latitude, -90 to 90"
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "longitude, -180 to 180"
}
},
"additionalProperties": false
},
"minItems": 2,
"description": "the points of the path in order, each with lat and lon"
},
"samples": {
"type": "integer",
"default": 0,
"minimum": 2,
"description": "number of samples along the path"
},
"interval_m": {
"type": "number",
"minimum": 10,
"description": "metres between samples, at least 10"
}
},
"additionalProperties": false
}geocode_reverseFinds the address or place at a point (reverse geocoding). detail chooses what to return: the nearest address or object (address, the default), the street, the district, the city, the county, the state or the country that contains the point. The result has the same fields as those of geocode_search. One call counts as one geocoding request.
read-only
geocode_reverse
Finds the address or place at a point (reverse geocoding). detail chooses what to return: the nearest address or object (address, the default), the street, the district, the city, the county, the state or the country that contains the point. The result has the same fields as those of geocode_search. One call counts as one geocoding request.
| Argument | Type | Description |
|---|---|---|
| lat* | number | latitude, -90 to 90 |
| lon* | number | longitude, -180 to 180 |
| detail | string | what to return |
| language | string | language of the names and addresses; the local names when not set |
Input schema (JSON)
{
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "latitude, -90 to 90"
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "longitude, -180 to 180"
},
"detail": {
"enum": [
"address",
"street",
"district",
"city",
"county",
"state",
"country"
],
"type": "string",
"description": "what to return"
},
"language": {
"enum": [
"en",
"de",
"fr"
],
"type": "string",
"description": "language of the names and addresses; the local names when not set"
}
},
"additionalProperties": false
}geocode_searchFinds places, addresses and points of interest by name (geocoding). Partial text works, as for autocomplete. Each result has the name, the address, lat and lon, a bounding box (south, west, north, east), the OpenStreetMap element (osm), and for ways and relations an overpass_area_id to use in overpass_query as area(id:N). Languages: en, de, fr. One call counts as one geocoding request.
read-only
geocode_search
Finds places, addresses and points of interest by name (geocoding). Partial text works, as for autocomplete. Each result has the name, the address, lat and lon, a bounding box (south, west, north, east), the OpenStreetMap element (osm), and for ways and relations an overpass_area_id to use in overpass_query as area(id:N). Languages: en, de, fr. One call counts as one geocoding request.
| Argument | Type | Description |
|---|---|---|
| kind | string | only places of this kind; settlement is a city, town, village or district |
| near | object | prefer results near this point |
| limit | integer | most results |
| query* | string | what to find, such as "Bundesplatz 3, Bern", "Zermatt" or "Louvre" |
| within | object | |
| language | string | language of the names and addresses; the local names when not set |
| country_codes | array | only results in these countries, ISO 3166-1 alpha-2 codes such as CH or DE |
Input schema (JSON)
{
"type": "object",
"required": [
"query"
],
"properties": {
"kind": {
"enum": [
"country",
"state",
"city",
"settlement"
],
"type": "string",
"description": "only places of this kind; settlement is a city, town, village or district"
},
"near": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "latitude, -90 to 90"
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "longitude, -180 to 180"
}
},
"description": "prefer results near this point",
"additionalProperties": false
},
"limit": {
"type": "integer",
"default": 5,
"maximum": 20,
"minimum": 1,
"description": "most results"
},
"query": {
"type": "string",
"description": "what to find, such as \"Bundesplatz 3, Bern\", \"Zermatt\" or \"Louvre\""
},
"within": {
"type": "object",
"required": [
"south",
"west",
"north",
"east"
],
"properties": {
"east": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "longitude"
},
"west": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "longitude"
},
"north": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "latitude"
},
"south": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "latitude"
}
},
"additionalProperties": false
},
"language": {
"enum": [
"en",
"de",
"fr"
],
"type": "string",
"description": "language of the names and addresses; the local names when not set"
},
"country_codes": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2,
"minLength": 2
},
"description": "only results in these countries, ISO 3166-1 alpha-2 codes such as CH or DE"
}
},
"additionalProperties": false
}overpass_examplesSearches the cookbook of overpass.ch: Overpass queries that were tested on the full planet, with explanations. Give a topic in a few words, such as "bakeries in a city", "hiking routes", "count buildings" or "changes since a date", and get the 5 closest examples with their query and a link. Free: it does not count as a request.
read-only
overpass_examples
Searches the cookbook of overpass.ch: Overpass queries that were tested on the full planet, with explanations. Give a topic in a few words, such as "bakeries in a city", "hiking routes", "count buildings" or "changes since a date", and get the 5 closest examples with their query and a link. Free: it does not count as a request.
| Argument | Type | Description |
|---|---|---|
| topic* | string | what the query should find, in a few English words |
Input schema (JSON)
{
"type": "object",
"required": [
"topic"
],
"properties": {
"topic": {
"type": "string",
"description": "what the query should find, in a few English words"
}
},
"additionalProperties": false
}overpass_queryRuns an Overpass QL query on the full OpenStreetMap planet at overpass.ch (minutely updates) and returns the matching nodes, ways and relations with their tags.
Start the query with a settings line such as [out:json][timeout:25]; JSON is used when the query does not set [out:]. [timeout:N] stops the query after N s: at most 120 s through this tool, and the plan may allow less.
Patterns:
- Box (south,west,north,east): nwr["amenity"="cafe"](47.36,8.53,47.38,8.55); out center;
- Radius in metres around lat,lon: nwr["amenity"="pharmacy"](around:1000,47.3769,8.5417); out center;
- In a place: overpass_area_id from geocode_search, then area(id:3600051701)->.a; nwr["tourism"="hotel"](area.a); out center;
- By name (exact, local language): area["name"="Wien"]["admin_level"="4"]->.a;
- Count: out count; Tags only: out tags; At most 50: out center 50; Lines with coordinates: out geom; (large)
- Regex, any case: ["name"~"^Bahnhof",i]
- By id: node(3470507586); out; way(id:1,2,3); out tags;
- The map at a past date (Medium and Large plans): [date:"2015-01-01T00:00:00Z"] in the settings line.
The answer starts with counts and the date of the data, then one JSON object per element and line, up to max_chars characters. When it is cut, call again with offset, or narrow the query. Each call counts as one request of the plan, a cut one too. Data © OpenStreetMap contributors, ODbL.
read-only
overpass_query
Runs an Overpass QL query on the full OpenStreetMap planet at overpass.ch (minutely updates) and returns the matching nodes, ways and relations with their tags. Start the query with a settings line such as [out:json][timeout:25]; JSON is used when the query does not set [out:]. [timeout:N] stops the query after N s: at most 120 s through this tool, and the plan may allow less. Patterns: - Box (south,west,north,east): nwr["amenity"="cafe"](47.36,8.53,47.38,8.55); out center; - Radius in metres around lat,lon: nwr["amenity"="pharmacy"](around:1000,47.3769,8.5417); out center; - In a place: overpass_area_id from geocode_search, then area(id:3600051701)->.a; nwr["tourism"="hotel"](area.a); out center; - By name (exact, local language): area["name"="Wien"]["admin_level"="4"]->.a; - Count: out count; Tags only: out tags; At most 50: out center 50; Lines with coordinates: out geom; (large) - Regex, any case: ["name"~"^Bahnhof",i] - By id: node(3470507586); out; way(id:1,2,3); out tags; - The map at a past date (Medium and Large plans): [date:"2015-01-01T00:00:00Z"] in the settings line. The answer starts with counts and the date of the data, then one JSON object per element and line, up to max_chars characters. When it is cut, call again with offset, or narrow the query. Each call counts as one request of the plan, a cut one too. Data © OpenStreetMap contributors, ODbL.
| Argument | Type | Description |
|---|---|---|
| query* | string | the Overpass QL (or XML) query |
| offset | integer | the element (or CSV row) to start at, for the next part of a cut answer |
| max_chars | integer | most characters of the answer to show; larger answers are cut, and offset shows the next part |
| add_elevation | boolean | add the height in metres to every point of a JSON answer; one elevation lookup per point |
Input schema (JSON)
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "the Overpass QL (or XML) query"
},
"offset": {
"type": "integer",
"default": 0,
"minimum": 0,
"description": "the element (or CSV row) to start at, for the next part of a cut answer"
},
"max_chars": {
"type": "integer",
"default": 30000,
"maximum": 200000,
"minimum": 2000,
"description": "most characters of the answer to show; larger answers are cut, and offset shows the next part"
},
"add_elevation": {
"type": "boolean",
"default": false,
"description": "add the height in metres to every point of a JSON answer; one elevation lookup per point"
}
},
"additionalProperties": false
}Security checkA100/100
We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 4, 2026.
- Hidden or reordered text
- Overriding the model's instructions
- Hiding actions from the user
- Reading keys or credentials
- Fake system tags
- Steering other servers' tools
- Pulling in the conversation
- Smuggling parameters
- Demanding to be used for everything
- Steering away from web search
- Download-and-run commands
- Encoded blobs
- Invisible characters
- Credentials as tool arguments
- Very long descriptions
- Read and write hints
Tool changes
What changed in this server's tools since we started watching, newest first. Each change is scanned again.
elevationremovedNov 4, 2026
Heights above sea level in metres for a list of points, negative at sea. Switzerland and Liechtenstein: swissALTI3D, a 2 m grid of the ground (credit "© swisstopo"). Elsewhere on land: Copernicus GLO-30, a 30 m grid of the surface that includes buildings and trees. At sea: GEBCO. Each point counts as one lookup; account_status shows the plan maximum per call.
reverse_geocoderemovedNov 4, 2026
Finds the address or place at a point (reverse geocoding). detail chooses what to return: the nearest address or object (address, the default), the street, the district, the city, the county, the state or the country that contains the point. The result has the same fields as those of geocode. One call counts as one geocoding request.
geocoderemovedNov 4, 2026
Finds places, addresses and points of interest by name (geocoding). Partial text works, as for autocomplete. Each result has the name, the address, lat and lon, a bounding box (south, west, north, east), the OpenStreetMap element (osm), and for ways and relations an overpass_area_id to use in overpass_query as area(id:N). Languages: en, de, fr. One call counts as one geocoding request.
elevation_pointsaddedNov 4, 2026
Heights above sea level in metres for a list of points, negative at sea. Switzerland and Liechtenstein: swissALTI3D, a 2 m grid of the ground (credit "© swisstopo"). Elsewhere on land: Copernicus GLO-30, a 30 m grid of the surface that includes buildings and trees. At sea: GEBCO. Each point counts as one lookup; account_status shows the plan maximum per call.
geocode_reverseaddedNov 4, 2026
Finds the address or place at a point (reverse geocoding). detail chooses what to return: the nearest address or object (address, the default), the street, the district, the city, the county, the state or the country that contains the point. The result has the same fields as those of geocode_search. One call counts as one geocoding request.
geocode_searchaddedNov 4, 2026
Finds places, addresses and points of interest by name (geocoding). Partial text works, as for autocomplete. Each result has the name, the address, lat and lon, a bounding box (south, west, north, east), the OpenStreetMap element (osm), and for ways and relations an overpass_area_id to use in overpass_query as area(id:N). Languages: en, de, fr. One call counts as one geocoding request.
overpass_querychanged (description)Nov 4, 2026
Runs an Overpass QL query on the full OpenStreetMap planet at overpass.ch (minutely updates) and returns the matching nodes, ways and relations with their tags. Start the query with a settings line such as [out:json][timeout:25]; JSON is used when the query does not set [out:]. [timeout:N] stops the query after N s: at most 120 s through this tool, and the plan may allow less. Patterns: - Box (south,west,north,east): nwr["amenity"="cafe"](47.36,8.53,47.38,8.55); out center; - Radius in metres around lat,lon: nwr["amenity"="pharmacy"](around:1000,47.3769,8.5417); out center; - In a place: overpass_area_id from
geocode,geocode_search, then area(id:3600051701)->.a; nwr["tourism"="hotel"](area.a); out center; - By name (exact, local language): area["name"="Wien"]["admin_level"="4"]->.a; - Count: out count; Tags only: out tags; At most 50: out center 50; Lines with coordinates: out geom; (large) - Regex, any case: ["name"~"^Bahnhof",i] - By id: node(3470507586); out; way(id:1,2,3); out tags; - The map at a past date (Medium and Large plans): [date:"2015-01-01T00:00:00Z"] in the settings line. The answer starts with counts and the date of the data, then one JSON object per element and line, up to max_chars characters. When it is cut, call again with offset, or narrow the query. Each call counts as one request of the plan, a cut one too. Data © OpenStreetMap contributors, ODbL.