Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
overpass.ch is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Overpass API on the full planet with history, plus geocoding and elevation. Needs an account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http overpass-ch-mcp https://api.overpass.ch/mcp --header 'X-API-Key: ${X_API_KEY}'
# 2 — ask your agent for something these tools do
# overpass_query, overpass_examples, geocode_search and 4 more
It needs X_API_KEY (API key from https://overpass.ch/dashboard/keys): this sends it in the X-API-Key header from your environment, so export it first — its endpoint answers 401 without it.
overpass.ch costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads X_API_KEY (API key from https://overpass.ch/dashboard/keys) from your environment each time it connects and sends it in the X-API-Key header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http overpass-ch-mcp https://api.overpass.ch/mcp --header 'X-API-Key: ${X_API_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: X-API-Key header — API key from https://overpass.ch/dashboard/keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 (sou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| add_elevation | boolean | no | add the height in metres to every point of a JSON answer; one elevation lookup per point |
| max_chars | integer | no | most characters of the answer to show; larger answers are cut, and offset shows the next part |
| offset | integer | no | the element (or CSV row) to start at, for the next part of a cut answer |
| query | string | yes | the Overpass QL (or XML) query |
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. It does not count as a request.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | what the query should find, in a few English words |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country_codes | array | no | only results in these countries, ISO 3166-1 alpha-2 codes such as CH or DE |
| kind | string | no | only places of this kind; settlement is a city, town, village or district |
| language | string | no | language of the names and addresses; the local names when not set |
| limit | integer | no | most results |
| near | object | no | prefer results near this point, such as a place named in the conversation |
| query | string | yes | what to find, such as "Bundesplatz 3, Bern", "Zermatt" or "Louvre" |
| within | object | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail | string | no | what to return |
| language | string | no | language of the names and addresses; the local names when not set |
| lat | number | yes | latitude, -90 to 90 |
| lon | number | yes | longitude, -180 to 180 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_chars | integer | no | most characters of the answer to show; larger answers are cut, and offset shows the next part |
| points | array | yes | the points, each with lat and lon |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| interval_m | number | no | metres between samples, at least 10 |
| path | array | yes | the points of the path in order, each with lat and lon |
| samples | integer | no | number of samples along the path |
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 names the products on a free plan, which is not for commercial use. It does not count as a request.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install overpass.ch or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
The scanner has read version 1.0.2 of this listing, but not the release on the shelf, so neither a grade nor a report is shown for it here. Nothing on this tab is ever borrowed from another release or another listing.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish overpass.ch can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.