A
licenseNot graded
qualityC
maintenanceEnables creating themed SVG maps, GeoJSON data, projections, React components, and embeddable map builders through natural language requests.
54 npm
MIT
@ultimaps/mcp
by ultimaps
Related Servers
Alternatives to @ultimaps/mcp
No user-submitted related servers found.
Related Servers
@maproll/mcpofficial
AlicenseAqualityBmaintenanceEnables agents to turn structured data into production-ready static maps, returning rendered PNG and SVG URLs along with an editable map link.437 npm4MIT- AlicenseNot gradedqualityDmaintenanceEnables geocoding, reverse geocoding, place search, nearby discovery, routing, and distance calculations using Mappls/MapMyIndia location data for India.17 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables geocoding, reverse geocoding, elevation profiles, static map PNGs, and coordinate reprojection using MapTiler's OpenStreetMap data.6 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables interactive map display with up to 50 marked places and optional route lines, using a bundled Leaflet UI and OpenStreetMap tiles.-
Magic Lane MCP Serverofficial
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.813 npm7Apache 2.0
TDQS
A4.6/5.0
Scored across 3 tools
Disambiguation5/5
The three tools split cleanly along action lines: list_maps enumerates available maps, get_map_regions inspects one map's regions, and render_map produces an image. The descriptions even pre-empt the most likely confusion by telling the agent it rarely needs get_map_regions before rendering and should only call list_maps when the id is unknown.
Naming Consistency5/5
All three follow a strict snake_case verb_noun pattern (render_map, get_map_regions, list_maps), with the verb accurately signalling the operation type. No mixing of conventions or vague verbs.
Tool Count4/5
Three tools is lean but each earns its place in a clear discover→inspect→render pipeline, and the server has a narrowly scoped domain. It sits just under the typical 3-15 comfort range, but nothing feels redundant or padded.
Completeness4/5
The core workflow is fully covered: enumerate maps, resolve/verify region keys, and render with validation via dryRun plus file output. Minor gaps exist around post-render management (no tool to fetch, re-edit, or delete previously rendered maps beyond the Studio link), but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues