ShowMeOnMap
Server Details
Ask in plain English, get a rendered, shareable map from live public data. 24 geospatial tools.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
24 toolsadd_annotationPlace an annotation on the map (direct)Inspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Stable id for this annotation — caller-supplied. | |
| color | No | Optional CSS color for the marker + label. | |
| label | No | Optional text rendered at the point. | |
| coords | Yes | [lng, lat] in WGS84. | |
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
add_fusion_layerAdd bivariate fusion layerInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | bivariate | |
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| layer_a_id | Yes | ||
| layer_b_id | Yes | ||
| new_layer_id | No | ||
| value_field_a | No | ||
| value_field_b | No |
add_layerAdd a layer (direct)Inspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| intent | No | Optional. Which mental model is this add_layer operating under? "primary-data" = the layer the user actually asked to see; "context-overlay" = supporting data layered on top of a primary; "reference-boundary" = admin/geo boundary used as a backdrop; "annotation" = caller-placed callout / pin layer; "comparison" = a layer added to compare against another; "other" = none of the above. | |
| map_id | Yes | map_id from a prior build_map call | |
| layerPlan | Yes | Full LayerPlan object. Must include id, title, source, viz, geometry. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
build_mapBuild a mapInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language: "coffee shops in Tokyo", "GDP by country", "volcanoes in Indonesia", etc. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
clear_filtersClear all filters on a layer (direct, gated)IdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| layerId | Yes | ||
| confirmed | No | Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Wiping a filter chain is recoverable via undo, but autonomous agents lack a UI surface to confirm intent. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
correlate_layersCompute correlation between two layersRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| layer_a_id | Yes | ||
| layer_b_id | Yes | ||
| value_field_a | No | ||
| value_field_b | No |
export_imageExport map as imageRead-onlyIdempotentInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | png | |
| legend | No | ||
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
export_layer_dataExport layer dataRead-onlyIdempotentInspect
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". URL is valid for 24 hours. Required: map_id, layer_id, format, rationale.
| Name | Required | Description | Default |
|---|---|---|---|
| format | Yes | ||
| map_id | Yes | ||
| layer_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
export_workspaceExport the workspace JSONRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
filter_layerFilter a layer (direct)Inspect
Narrow a layer to features matching a structured predicate. append:true (default) conjoins with any existing filter; append:false replaces the chain.
| Name | Required | Description | Default |
|---|---|---|---|
| append | No | Default true. false replaces the layer's existing filter chain. | |
| intent | No | Optional. Which mental model is this filter operating under? "narrow" = generic shrink-the-set; "isolate-outliers" = pull out anomalies for inspection; "compare-subset" = pre-step before a side-by-side compare; "preview-data" = exploratory peek; "other" = none of the above. | |
| map_id | Yes | ||
| layerId | Yes | id of the layer to filter | |
| predicate | Yes | Predicate in the Mongo-shape grammar. Examples: {op:"eq",field:"category",value:"cafe"}, {op:"gt",field:"magnitude",value:5}, {op:"within",geometry:{type:"Polygon",coordinates:[...]}}, {op:"and",children:[...]}. See docs/superpowers/specs/2026-04-17-workspace-ops-log-design.md §6. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
get_stateRead map stateRead-onlyIdempotentInspect
Return the current workspace, map plan, and active filters for a given map_id.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
mutate_mapMutate a mapInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | map_id from a prior build_map call | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| instruction | Yes | e.g., "filter to where magnitude is greater than 5", "change basemap to dark" |
query_featuresQuery features from a layer (read-only)Read-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Default 100, max 1000. Response sets `truncated:true` when clipped. | |
| map_id | Yes | ||
| layerId | Yes | ||
| predicate | Yes | Predicate in the Mongo-shape grammar. Examples: {op:"eq",field:"category",value:"cafe"}, {op:"gt",field:"magnitude",value:5}, {op:"within",geometry:{type:"Polygon",coordinates:[...]}}, {op:"and",children:[...]}. See docs/superpowers/specs/2026-04-17-workspace-ops-log-design.md §6. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
redoRedo a previously-undone opInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
remove_annotationRemove an annotation (direct)IdempotentInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| annotationId | Yes |
remove_layerRemove a layer (direct, destructive)DestructiveIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| layerId | Yes | ||
| confirmed | No | Set to true to confirm this destructive action. If omitted or false, the call returns a needs_confirmation envelope. Layer ids are tombstoned — once removed, the same id cannot be re-added later in this workspace. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
rename_layerRename a layer (direct)IdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| newLayerId | Yes | New id. Must be unique within the workspace. | |
| oldLayerId | Yes |
report_blockerReport a blocker (agent feedback)Read-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | No | Optional. The map_id you were working on, if any. | |
| what_i_tried | Yes | Which tools / inputs you attempted, in order. Be specific — tool name + key arg shape is ideal. | |
| what_i_was_trying | Yes | High-level intent in one or two sentences. e.g. "merge two filtered choropleths into a fused bivariate map". | |
| where_i_got_stuck | Yes | The specific failure: what came back, what was missing, why you could not proceed. | |
| suggested_capability | No | Optional. A new tool, op, or schema field that would have unblocked you. |
restyle_layerRestyle a layer (direct)IdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| color | No | CSS color string: hex (#RRGGBB), rgb/rgba, or named color. | |
| map_id | Yes | ||
| layerId | Yes | ||
| opacity | No | 0 (transparent) to 1 (opaque). | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
select_withinSubset a layer to a polygon selectionRead-onlyIdempotentInspect
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."
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| selection | Yes | GeoJSON Polygon or MultiPolygon in [lng,lat] coordinate order. | |
| newLayerId | Yes | Id for the new layer. Must not already be in use in this workspace. | |
| inheritStyle | No | Default true. false emits a new layer with minimal default styling. | |
| sourceLayerId | Yes |
set_cameraSet the map camera (direct)IdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| camera | Yes | ||
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
set_timeSet the time window (direct)IdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| field | Yes | Feature property carrying the time value (e.g. "date", "year", "timestamp"). | |
| format | No | How rangeStart/rangeEnd encode time. Default: unix_ms at render time. | |
| map_id | Yes | ||
| rangeEnd | Yes | Inclusive upper bound of the visible window. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. | |
| rangeStart | Yes | Inclusive lower bound of the visible window. |
tagSave a named checkpoint (direct)Inspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Checkpoint label, e.g. "before EV layer added" or "v1.0". | |
| map_id | Yes | ||
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
undoUndo the most recent op (gated)Inspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | ||
| confirmed | No | Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Autonomous undo without user intent is a footgun — an agent that decides to "fix" something can erase prior work. | |
| rationale | Yes | Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!