A
licenseA
qualityD
maintenanceProvides 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.
4
12 npm
2
Apache 2.0
inavi-mcp
OfficialRelated Servers
Alternatives to inavi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceUnified 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 gradedqualityAmaintenanceMCP Server for the Google Maps API.11,868 npm90,629MIT
- 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.30153 npm5MIT
- 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.1225 npm1MIT
TDQS
A4.7/5.0
Scored across 6 tools
Disambiguation5/5
Each tool maps cleanly to one of three resource types (map examples, REST API specs, SDK docs) paired with a list/get action. There is no meaningful overlap: list tools browse summaries, get tools retrieve details, and the resource domains are clearly distinct.
Naming Consistency5/5
All tool names follow a consistent list_<resource> / get_<resource> snake_case pattern. The singular/plural pairing (list_map_examples/get_map_example, list_api_specs/get_api_spec, list_sdk_docs/get_sdk_doc) is uniform and predictable.
Tool Count5/5
Six tools is well-scoped for a documentation lookup server: three browse tools and three corresponding detail-fetch tools. Each tool earns its place and there is no redundancy or bloat.
Completeness5/5
The server fully covers its documented workflow: browse and retrieve map examples, browse and retrieve REST API specs, and browse and retrieve SDK documentation. Category filtering and retry instructions prevent dead ends, and no obvious missing operation is apparent for the stated purpose.
Maintenance
ActivityActive
ResponsivenessNo issues