Overture Maps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server host (SSE/HTTP only) | 0.0.0.0 |
| PORT | No | Server port (SSE/HTTP only) | 8000 |
| TOOL_MODE | No | Tool mode: direct or progressive | direct |
| TRANSPORT | No | Transport type: stdio, sse, or http | stdio |
| MAX_RADIUS_M | No | Safety cap on radius (meters) | 50000 |
| OVERTURE_API_KEY | No | Bearer token for client auth (required for SSE/HTTP transport) | |
| OVERTURE_DATA_VERSION | No | Overture release version | 2026-01-21.0 |
| MAX_CONCURRENT_QUERIES | No | DuckDB concurrency limit | 3 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_place_categoriesA | Search and browse the Overture Maps place category taxonomy |
| places_in_radiusB | Find all places matching a category within a radius of a point |
| nearest_place_of_typeB | Find the single closest place of a given type to a point |
| count_places_by_type_in_radiusA | Count how many places of a category exist within a radius |
| building_count_in_radiusB | Count total buildings within a radius of a point |
| building_class_compositionC | Get the percentage breakdown of building types within a radius |
| point_in_admin_boundaryB | Determine what administrative boundaries contain a given point |
| road_count_by_classB | Count road segments by class within a radius of a point |
| nearest_road_of_classC | Find the single closest road segment of a given class to a point |
| road_surface_compositionA | Get the percentage breakdown of road surface types within a radius |
| land_use_at_pointC | Determine the land use designation at a specific point |
| land_use_compositionB | Get the percentage breakdown of land use types within a radius |
| land_use_searchC | Find land use parcels of a specific subtype within a radius |
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 13 tools
Each tool targets a distinct combination of data type and operation. Place queries separate count, nearest, and all-in-radius; building, road, and land use tools likewise have unique analytical purposes. No two tools overlap in function.
Snake_case is used throughout, and names are generally descriptive. However, some tools begin with verbs (get_, count_) while others use noun phrases (places_in_radius, building_class_composition), making the pattern not fully uniform. Within each data type, naming is predictable.
13 tools is well-scoped for a geospatial server covering places, buildings, roads, land use, and administrative boundaries. Each tool has a clear purpose and the count feels neither sparse nor excessive.
The set provides comprehensive read-only coverage of Overture Maps data themes: place category browsing and spatial queries, building aggregates, road analysis, land use queries, and boundary containment. All typical geospatial analytics are supported, with no obvious dead ends.