mcpbeat

ShowMeOnMap MCP Server

com.showmeonmap/maps
answering

ShowMeOnMap is answering right now. Last checked 8 min ago. 66 installs a week from npm. It exposes 24 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 355 · avg 18 · -16% w/w
a month agotoday
Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
24
Tools
read from the server
765 ms
Response time
average over 24h
66
Installs / week
npm and PyPI

Connect this server

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

run in your terminal
claude mcp add maps --transport http https://showmeonmap.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "maps": {
      "url": "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
{
  "mcpServers": {
    "maps": {
      "url": "https://showmeonmap.com/api/mcp"
    }
  }
}

Available tools 24

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, rationale. 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 — treat it as shareable-forever, not temporary. Required: map_id, layer_id, format, rationale.
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. Use this when you want the full raw state for serialization; use get_state when you want the compact envelope 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, ... }. Prefer this when you already have a structured plan; otherwise use mutate_map. For the full LayerPlan and Op spec, fetch 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.
build
build_map
Create a new workspace from a natural-language query. Returns a map_id you can pass to mutate_map or get_state for follow-up actions. For the full Op catalog and predicate grammar that downstream tools (mutate_map, filter_layer, etc.) accept, fetch the MCP resource at showmeonmap://docs/workspace-ops-spec — do NOT guess the shapes.
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). Use for "zoom to Japan", "center on Paris at z=10", or finishing a drill-down after filter_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. Use this when you want a numeric answer without rendering; use add_fusion_layer when the user wants the visualization. Required: map_id, layer_a_id, layer_b_id, rationale.
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.
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 (call build_map or add_layer first). 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, rationale.
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. For the full Op catalog and predicate grammar, fetch 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
Tell the ShowMeOnMap team your agent hit something it could not accomplish — an unsupported intent, a missing tool, an unclear schema, an op that failed in a confusing way. Use this when build_map / mutate_map / a direct-op tool returns something you cannot recover from, OR when you would have wanted a different tool to exist. Records the report to a server-side log; does not unblock the current session, but feeds future capability work. No map_id required — file the report even if no map was built.
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.
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. Use for "filter to 2020-2024" or "show only the last 7 days" intents. 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.

Endpoints

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

ShowMeOnMap — questions

Answers built from our own checks of this server.

What can ShowMeOnMap do?
It exposes 24 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 18 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, layer and annotation. 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 91 of 91 checks got a reply (100.0%), average response time 765 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 with the file path 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 24 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 765 ms on average, which is faster than 10% 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 66 times in the last week. Week over week that is -16%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.