@ultimaps/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ULTIMAPS_API_KEY | No | API key from Studio → Workspace → API. An invalid key is an error and never falls back to keyless. | |
| ULTIMAPS_API_URL | No | Point at a local API during development (http://localhost:3001). Plain http is only accepted for localhost. | https://api.ultimaps.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mapsA | List the maps Ultimaps can render: the world, continents, countries subdivided into states, provinces, counties or departments, and US ZIP code areas.
Each row is {id, title, regionType, layers, regionCount, labels}. |
| get_map_regionsA | Look up one map: title, regionType, regionCount, labels, layers, and its regions as {key, title}, 200 per page.
You rarely need this before rendering. render_map accepts region names, codes and common aliases and auto-corrects typos, reporting what it matched.
Use it to build a dataset covering every region of a map, to see how a map names its regions, or to resolve a key render_map could not match.
|
| render_mapA | Render a map of the world, a continent, a country, its states/provinces/counties, or US ZIP code areas as an image shown in the conversation. Color regions with ONE of these (choropleth and categories are mutually exclusive):
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: list_maps enumerates available maps, get_map_regions retrieves detailed region data for a specific map, and render_map produces an image. There is no overlap that would confuse an agent selecting a tool for a task.
All tool names follow a consistent verb_noun pattern: list_maps, get_map_regions, render_map. The pattern is uniform and predictable, making it easy to infer function from name.
Three tools is a well-scoped count for a map rendering service. Each tool covers a necessary part of the workflow—discover, inspect, and render—without unnecessary bloat or gaps.
The tool surface fully covers the intended domain: it allows listing available maps, fetching region details, and rendering maps with extensive customization. Additional operations like map editing or management are out of scope, so the set is complete for its stated purpose.