inavi-mcp
OfficialRelated Servers
Alternatives to inavi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides Naver Map API functions (geocoding, reverse geocoding, directions, static map, and usage queries) as MCP tools for use in Claude Desktop, VS Code, and other MCP clients.426 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceUnified MCP server for place search and geocoding across Kakao, Naver, and Google Maps APIs with automatic provider fallback.MIT
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server for Google Maps APIs, enabling geocoding, place search and details, distance matrix, elevation, and directions through natural language.6-
- -licenseNot gradedqualityBmaintenanceMCP Server for the Google Maps API.11,868 npm91,952MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search places and addresses, compute driving, walking, and kickboard routes, optimize waypoints, and calculate distance and time matrices. Results can be displayed as interactive maps within conversations.1267 npmMIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server providing 30 tools for geocoding, routing, and OpenStreetMap data analysis. It enables AI assistants to search for locations, calculate travel routes, and perform quality assurance checks on map data.30972 npm6MIT
TDQS
Scored across 6 tools
The six tools form three clear list/get pairs for distinct resources: map examples, REST API specs, and SDK docs. Descriptions explicitly distinguish workflows and warn that examples contain the SDK loader while SDK docs do not, so an agent can select the right tool.
All tools follow a consistent verb_noun pattern: list_map_examples, get_map_example, list_api_specs, get_api_spec, list_sdk_docs, get_sdk_doc. Plural list names and singular get names are predictable and readable.
Six tools is well-scoped for a reference/documentation server. Each tool earns its place as either a browsing or retrieval operation for one of the three resource categories.
The surface provides browse-and-retrieve coverage for examples, API specs, and SDK docs, which covers the core documentation workflow. Minor gaps may exist around direct search or category listing, but agents can work around them via list filters and retries without category.