mcpbeat Sign in

ShowMeOnMap MCP Server

by showmeonmap Your server? Claim it
answering

ShowMeOnMap is answering right now. Last checked 2 min ago. 489 installs a week from npm. It exposes 30 tools.

Ask in plain English, get a rendered, shareable map from live public data. 24 geospatial tools.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 203 · avg 20 · +1258% w/w
a month agotoday
Uptime history 91 days of history · worst day 71%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
30
Tools
read from the server
1296 ms
Response time
average over 24h
489
Installs / week
npm and PyPI

What changed 72

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

2 Nov a tool changed the parameters it asks for run_analysis
26 Oct a tool description was rewritten build_map
26 Oct a tool changed the parameters it asks for build_map
8 Oct 10 tool descriptions were rewritten add_fusion_layer, add_layer, build_map and 7 more
8 Oct 2 tools changed the parameters they ask for clear_filters, undo
7 Oct a tool description was rewritten build_map
7 Oct a tool appeared get_map_view
29 Sep 29 tools changed the parameters they ask for31 times that day add_annotation, add_fusion_layer, add_layer and 26 more
28 Sep 3 tool descriptions were rewritten add_layer, build_map, mutate_map
31 Aug 2 tool descriptions were rewritten5 times that day run_analysis, run_workflow
and 21 more, back to 11 August 2026

ShowMeOnMap missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add maps --transport http https://showmeonmap.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://showmeonmap.com/api/mcp
~/.codex/config.toml
[mcp_servers.maps]
url = "https://showmeonmap.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "maps": {
      "url": "https://showmeonmap.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "maps": {
      "type": "http",
      "url": "https://showmeonmap.com/api/mcp"
    }
  }
}

Available tools 30

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

export
export_image
Returns a deep-link URL that opens the map in the user's browser and automatically triggers a PNG download. The user clicks the link, the browser renders the map at full resolution with the legend composited (if legend: true), and the file downloads. There is no server-side rendering; the user's browser is the renderer. Required: map_id. Optional: format (png default), legend (true default).
export_layer_data
Export a single layer's features as a downloadable file. Returns a URL with Content-Disposition: attachment so the user's browser downloads it. CSV drops geometry beyond a (lng, lat) centroid — for full polygon/line geometry, use format: "geojson". The URL is an unguessable capability link that does NOT expire: anyone with the link can download the file. Required: map_id, layer_id, format.
export_workspace
Return the current workspace document (ops log + cursor + meta) plus the materialized mapPlan and layerFilters, in a shape suitable for save-to-file / share-by-URL / inspection. Pure read — no mutation, no credit charge. This is the full raw state for serialization; get_state returns a compact summary for display.
annotation
add_annotation
Add a user-placed label at a specific coordinate. Annotations are independent of layers and live in their own id namespace. Strict: the id must not already be in use by another CURRENTLY-placed annotation (removed ids can be recycled).
remove_annotation
Drop a previously-placed annotation by id. Strict: removing an already-removed or never-placed id fails. After removal, the id CAN be re-used by a later add_annotation (unlike layer ids, which are tombstoned for the session).
layer
add_layer
Append a fully-constructed LayerPlan to an existing workspace without going through NL. Pass the same shape the workspace pipeline emits — { id, title, source, viz, geometry, ... }. Takes a structured plan; natural-language edits go through mutate_map. The full LayerPlan and Op spec are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.
remove_layer
Drop a layer from the workspace by id. Strict: removing an already-removed or never-added layer fails. Layer ids do NOT recycle — a removed id cannot be re-added later in the same workspace. GATED: this tool is destructive. Pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.
analysis
run_analysis
Compute a spatial analysis server-side and append the finished, honestly-legended result as a new layer + camera; the result REPLACES its input layer(s) (undoable). hotspot = Getis-Ord Gi*: hot/cold significance classes (99/95/90%, Benjamini-Hochberg FDR-corrected) on a numeric field, or on hex-binned point density when valueField is omitted. zonal = aggregate points into polygon zones (an existing zone layer OR a generated h3 fishnet): count/sum/mean/min/max per zone as a quantile choropleth where zero and no-data are distinct classes. enrich = join a US Census ACS indicator (median income, home value, rent, …) onto each feature by tract/county/state containment — unmatched features stay null, never zero-filled. join = spatial join (attribute transfer): each point in layerId takes properties from the joinLayerId polygon containing it (collisions prefixed, unmatched points carry NO joined fields, zero overlap is a typed rejection). merge = append two same-geometry-class layers into one dataset with a per-row source column (schemas never null-filled; class mismatch is a typed failure). near = nearest-neighbor distance columns (great-circle meters, stated — never presented as road distance). dissolve = true polygon union per attribute group (missing values form their own group; partial sums reported). Returns a grounded memo + stats payload — every number is computed, never generated; findings keep the map. Costs 1 credit when the result lands; typed failures (unknown layer, too few features, >10,000-feature cap) are refunded.
build
build_map
Make an interactive, data-driven map from a plain-language request, built from live public data with every value cited to its source. Covers natural hazards (earthquakes, wildfires, volcanoes, tropical storms, floods), weather and air quality, statistics by country, state or region (GDP, population, health, emissions — World Bank, Eurostat, US Census), infrastructure and transit (railways, power plants, transit lines, roads), parks and terrain, and points of interest from OpenStreetMap. The query carries the place, time window and any thresholds — "earthquakes above magnitude 5 near Japan this month", "GDP per capita across Europe" — and the server applies them itself. Returns a shareable link and a map_id for follow-ups (mutate_map, filter_layer, get_state); in clients that support MCP Apps the map also renders interactively in the conversation. Analysis maps (site selection, spatial analysis) can take one to three minutes: when the build outlasts one call it returns status "building" with a resume_token, and calling build_map again with the same query and that resume_token collects the map without spending credits. The Op catalog and predicate grammar that downstream tools (mutate_map, filter_layer, etc.) accept are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.
camera
set_camera
Override the workspace camera. Latest set_camera op wins during replay. Two modes: `fitBounds` with a [w,s,e,n] bbox (plus optional padding/animateMs), or `flyTo` with [lng,lat] center + zoom (plus optional pitch/bearing/animateMs). Covers requests like "zoom to Japan", "center on Paris at z=10", or framing a filtered layer. Equivalent to the camera move mutate_map would emit, but skips the NL roundtrip.
clear
clear_filters
Wipe every predicate currently applied to a layer's filter chain, making every source feature visible again. Inverse of filter_layer. No-op on layers that have no existing filter. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.
correlate
correlate_layers
Spatially join two existing workspace layers and return the Pearson correlation coefficient r, sample size n, two-sided p-value approximation, plus human-readable strength and direction labels. Pure read — no layer is added, no op is committed, no credit charge. Returns numbers only; add_fusion_layer renders the same join as a map layer. Required: map_id, layer_a_id, layer_b_id.
features
query_features
Evaluate a predicate against a layer's inline features and return the matching subset. No Op is emitted and the workspace is not mutated. Handy for introspection ("how many X match Y?") before deciding whether to filter, subset, or build a new layer.
filter
filter_layer
Narrow a layer to features matching a structured predicate. `append:true` (default) conjoins with any existing filter; `append:false` replaces the chain.
focus
focus_area
Refine an existing layer to a NAMED area the server resolves from OpenStreetMap — a street corridor ("Broadway from Arbutus Street to Main Street"), a place ("Mount Pleasant"), or an intersection surroundings. Pass names only, never coordinates; unresolvable names return a clarification with real nearby candidates instead of guessed geometry. Emits ordinary undoable ops (filter / new layer + camera) and a grounded summary like "kept 37 of 150 features". Costs 1 credit when a mutation lands; clarifications are refunded.
fusion
add_fusion_layer
Spatially join two existing layers and add a new layer that encodes both values per region as a 3x3 bivariate choropleth. Both layers must already exist in the workspace. Auto-detects the numeric value field from each layer's viz config; pass value_field_a / value_field_b to override. Returns the new layer_id, correlation r, and matched-feature count. Required: map_id, layer_a_id, layer_b_id.
map
get_map_view
Used by the ShowMeOnMap map card to load a map version. Not for the model.
mutate
mutate_map
Apply a natural-language instruction to an existing workspace. Valid mutations: filter a layer, remove a layer, change camera, change basemap. For ambiguous instructions the tool emits a clarification field. For unrelated instructions it emits outOfScope — build a new map in that case. The full Op catalog and predicate grammar are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.
redo
redo
Advance the workspace cursor by one toward the tail of the ops log, replaying the next op that was previously undone. Calling redo when the cursor is already at the tail (no undone ops to fast-forward) fails rather than silently no-op. Note: any new op applied via apply-op / mutate-map after an undo truncates the redo tail (standard edit-stack semantics).
rename
rename_layer
Change a layer's id from oldLayerId to newLayerId. Re-keys any existing filter chain and preserves insertion order among sibling layers. Strict: newLayerId must not already be in use (current OR tombstoned) in this workspace. Subsequent ops must reference the layer by its new id.
report
report_blocker
Send the ShowMeOnMap team a report about a request this server could not complete — an unsupported intent, a missing tool, an unclear schema, or an op that failed in a confusing way. Records the report to a server-side log for future capability work; it does not change the current map or session. map_id is optional, so a report can be filed before any map exists.
restyle
restyle_layer
Adjust a layer's color and/or opacity. Within-palette changes only — the renderer silently ignores fields the current viz variant doesn't support. Pass at least one of color / opacity; passing neither is an accepted no-op.
save
save_workflow
Save a re-runnable, parameterized workflow: an ordered list of natural-language instructions (step 1 builds, later steps mutate). Wrap values in {braces} and declare them in params. Running it later re-executes the instructions on FRESH data and bills per step like typing.
select
select_within
Create a new layer containing the source layer's features that lie within the supplied polygon. The source layer is untouched. Useful for "show me only the X inside this country/bbox/hand-drawn shape."
state
get_state
Return the current workspace, map plan, and active filters for a given map_id.
tag
tag
Label the current workspace state with a user-supplied name. The label is mirrored into workspace.meta.tags so UIs can render a named-revision history. Tagging the same label twice is idempotent — no error, no duplicate entry.
time
set_time
Override the current time-range filter. Latest set_time op wins during replay. Covers requests like "filter to 2020-2024" or "show only the last 7 days". Not yet consumed by the renderer — the UI drives the slider directly — but the value is captured in the ops log and queryable via get_state.
undo
undo
Rewind the workspace cursor by one, re-materializing the state as it was before the last mutation. Does NOT delete any ops — redo will fast-forward. Calling undo at the workspace genesis (cursor === 0, only the CreateWorkspace op is in scope) is a no-op that surfaces an error rather than silently doing nothing. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.
workflow
run_workflow
Execute a saved workflow with parameter values. PAID: bills ~1 credit per step through the normal build/mutate paths (the estimate is in list_workflows). Optional batch mode sweeps ONE param across 2–20 values — each value is a full independent run (steps × values credits); failed/paused values are reported per value and the batch continues. A clarification pauses a single run (status "paused" + the question); failures stop at the failing step. On success the result is a live map with a shareable URL (batch: the last successful value's map).
workflows
list_workflows
List the caller's saved workflows with their parameters and per-run credit estimates.

Endpoints

URLTransportStateLatencyChecked
https://showmeonmap.com/api/mcp streamable-http answering 1174 ms 2 min ago

Alternatives to ShowMeOnMap

same job, measured the same way
Ferric Fred MCP
by ojhermann-org

MCP server for FRED (Federal Reserve Economic Data): full read API plus GeoFRED, 34 tools.

local only
Spain Open Data
by digvijaysingh-ai

Market sizing, prices, rents, crime and locations in Spain from INE and other public data

170 installs/wk 13 tools answering
CougarMap
by bryantclark

Find trail-camera spots for mountain lions from free public map data, ranked and explained.

local only
Geobble
by geobble

Geospatial workspace: manage sources and maps, run spatial analysis, and publish interactive maps

66 tools answering
Earth
by mireye

Mireye Earth: free public geospatial data, parcel enrichment, search, and cited answers.

answering
G
Googleapis
by googleapis-mapstools

Ground your AI applications with trusted geospatial data from Google Maps.

5 tools answering
P
Pubdata MCP
by autosha-blip

Free live public data (weather, quakes, ISS) plus one spend-capped paid tool.

98 installs/wk local only
mcp-belgium
by lacausecrypto

Single MCP server for Belgian public transport, statistics, open data, and geospatial services.

77 installs/wk local only

ShowMeOnMap — questions

Answers built from our own checks of this server.

What can ShowMeOnMap do?
It exposes 30 tools, read directly from the server on our last check. Among them: add_annotation, add_fusion_layer, add_layer, build_map, clear_filters, correlate_layers and 24 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is ShowMeOnMap mostly used for?
Its tools cluster around export, annotation and layer. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is ShowMeOnMap working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1296 ms. The bar chart above shows every period we have measured.
Is ShowMeOnMap still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect ShowMeOnMap?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ShowMeOnMap need an API key?
No. ShowMeOnMap completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 30 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ShowMeOnMap?
It answers our handshake in 1296 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use ShowMeOnMap?
The npm package @showmeonmap/mcp was installed 489 times in the last week. Week over week that is +1258%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.