Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Close API 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.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Walk, bike, and transit travel times from every US census block to nearby amenities.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http close-api-mcp https://mcp.close.city/mcp
# 2 — ask your agent for something these tools do
# find_place, get_catalog, walkability_summary and 7 more
Close API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MCAll 1 server
mcp.close.city1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 mcp add --scope user --transport http close-api-mcp https://mcp.close.city/mcpReconnect, 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.
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
10 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.
Look up a US city or town by name (free, no key). Returns matches with their census place GEOID and centre point (lon/lat). The entry point: feed a GEOID to blocks_in_area, or a centre to walkability_summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | City or town name, e.g. 'Providence'. |
| limit | integer | no | Max matches (1-20). |
List the travel modes and the destination-type taxonomy (free, no key). Use it to resolve type names to the numeric ids the other tools take. Modes are walk, bike, transit — there is no drive mode.
No parameter schema on file.
Fastest travel time from a location to each destination category, by mode (metered: 1 token per returned row). One origin: block_geoid or lat+lon. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, with rows tagged by origin. Batching saves requests and context, not tokens: it still charges per row. A non-empty truncated (+ truncated_reason) means the bal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block_geoid | string | no | 15-digit census block GEOID. |
| lat | number | no | — |
| lon | number | no | — |
| block_geoids | array | no | Many block GEOIDs — one batch call. |
| points | array | no | Many lat/lon points — one batch call. |
| mode | string | no | walk, bike, or transit. Omit for all three. |
Nearby points of interest and the travel time to each, from a location (metered: 1 token per returned row). One origin: block_geoid or lat+lon; keep limit small to control spend and context size. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, rows tagged by origin, no limit/pagination, so filter with type/mode/max_minutes. Batching saves requests and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block_geoid | string | no | — |
| lat | number | no | — |
| lon | number | no | — |
| block_geoids | array | no | Many block GEOIDs — one batch call. |
| points | array | no | Many lat/lon points — one batch call. |
| type | integer | no | Destination type id (see get_catalog). |
| mode | string | no | walk, bike, or transit. |
| max_minutes | integer | no | Upper bound on travel time (<=30). |
| limit | integer | no | Max rows (first page). |
The area reachable from a location within a time budget, as GeoJSON contours (metered: 10 tokens per contour). Give block_geoid or lat+lon. Defaults to a single 30-minute contour; ask for more only when needed (bodies can be large).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block_geoid | string | no | — |
| lat | number | no | — |
| lon | number | no | — |
| mode | string | no | walk, bike, or transit. |
| minutes | integer | no | A single threshold (1-60). |
| contours | array | no | Up to four ascending thresholds, instead of minutes. |
| direction | string | no | 'from' the origin (default) or 'to' it. |
Per-block travel times for every census block in an area (metered: 1 token per returned row). Give place_geoid (from find_place) for a whole city, or center {lat, lon} + radius_m. Rows carry a numeric mode_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_geoid | string | no | Census place GEOID (a whole city/town). |
| lat | number | no | Circle centre latitude (with lon + radius_m). |
| lon | number | no | Circle centre longitude. |
| radius_m | number | no | Circle radius in metres (<=28000). |
| type | integer | no | Destination type id (see get_catalog). |
| mode | string | no | walk, bike, or transit. |
| limit | integer | no | Max rows (first page). |
Check the token balance of the API key in use, without spending any tokens. Works even at a zero balance. Requires the Authorization bearer key.
No parameter schema on file.
Start free sign-up for the user: email them a six-digit code. The user must read the code from their own inbox and give it to you, then call redeem_code. This is how an agent gets the user an API key (5,000 free tokens, no card).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The user's email address. |
Complete sign-up with the six-digit code the user received, and return a new API key (shown once). Call request_sign_in first. The key grants 5,000 free tokens; store it and pass it as the Authorization bearer on future calls.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| code | string | yes | The six-digit code from the email. |
| label | string | no | Optional label for the key. |
Get a Stripe Checkout URL for the Close+ membership ($10/month: 5,000 API tokens granted monthly plus member features on the close.city map). The user pays in their own browser: give them the returned URL and stop. Needs a fresh six-digit code from request_sign_in, read by the user from their own inbox.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| code | string | yes | The six-digit code from the email. |
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 Close API 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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.2.0.
1.2.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 Close API 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.