MapNetwork MCP Server
Related Servers
Alternatives to MapNetwork MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceConverts addresses to GPS coordinates and creates map visualizations using the Geoapify API, allowing Claude users to generate GeoJSON data and map images from location lists.4-
- FlicenseNot gradedqualityBmaintenanceMCP server that enables LLMs to create and control interactive MapLibre maps by placing markers, drawing paths, and rendering polygons directly in Claude Desktop.-
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that wraps the Amap (高德地图) Web Service APIs, giving AI assistants like Claude Code 9 map tools: geocoding, route planning (driving/transit/walking/cycling), POI search, nearby search, distance measurement, and IP location.1227 npmMIT
- AlicenseAqualityDmaintenanceTurn GPS coordinates into place name, category, and live opening hours via OpenStreetMap. Works in Claude, Hermes Agent, OpenClaw, and any MCP client.11MIT
- FlicenseAqualityCmaintenanceGives Claude and other MCP clients access to Google Maps Platform: geocoding, place search, place details, directions, distance matrix, and elevation.7-
- AlicenseNot gradedqualityCmaintenanceEnables creating themed SVG maps, GeoJSON data, projections, React components, and embeddable map builders through natural language requests.179 npmMIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct operation: single-place maps, multi-marker maps, route maps, downloading a pending result, and re-downloading with different styling. The overlap between generate_map and generate_markers_map is minimal and the descriptions make the boundary clear.
All tool names follow a consistent verb_noun pattern using snake_case: generate_map, generate_markers_map, generate_route_map, download_map, redownload_map. The verb prefix clearly communicates the action while the noun identifies the target.
Five tools is well-scoped for a map generation server. Each tool covers a necessary part of the workflow—generating different map types, fetching results, and re-styling prior outputs—without redundancy or bloat.
The tool surface covers the full expected lifecycle: generate maps in three distinct forms, retrieve the async result, and re-download existing maps in alternate themes or formats. There are no obvious dead ends or missing core operations for the declared purpose.