Inavi MCP

What inavi-mcp does

inavi-mcp gives an AI assistant structured access to iNAVI Maps development material for South Korea. Its coverage includes location APIs for place and address search, geocoding, spatial queries, what3words, route directions, route optimization, map matching, and distance or time matrices. It also covers the iNAVI Maps Web JavaScript SDK.

The server is intended to help an agent inspect specifications and produce implementation code. It does not replace the application key required by a rendered map page, and its API-specification workflow is for understanding and writing API requests rather than directly calling those services.

How it works

The six tools are arranged as three browse-then-detail pairs:

• list_api_specs finds available APIs, optionally by category; get_api_spec returns the selected operation's full request and response specification.
• list_map_examples finds HTML examples by category; get_map_example returns the selected template and its metadata.
• list_sdk_docs finds SDK classes, methods, and types; get_sdk_doc returns documentation for a symbol or method.

Use the listing tool before the detail tool. For example, obtain an API operationId from list_api_specs before requesting its specification. If a category filter produces no useful result, search without the filter. The same fallback applies to map examples and SDK symbols.

Setup and configuration

The package can run through the standard MCP stdio configuration:

{
  "mcpServers": {
    "inavi-maps-mcp": {
      "command": "npx",
      "args": ["-y", "@inavi-maps/mcp-server"]
    }
  }
}

Node.js 22 or newer is required for the npx installation. The repository also provides an .mcpb bundle for Claude Desktop: download the latest bundle from the project's GitHub releases, open it or drag it into Claude Desktop, and restart the client. Setup instructions are also provided for Cursor, VS Code, Claude Code, Codex, and Windsurf.

Tools and capabilities

list_api_specs and get_api_spec expose OAS-based iNAVI Maps API definitions, including parameters, request bodies, and response schemas. References in returned schemas are expanded. API categories include search, geocoding, routing, optimization, map matching, and route matrices.

list_map_examples and get_map_example provide 18 render-ready HTML templates covering dynamic maps, markers, marker clustering, info windows, circles, polygons, multipolygons, and polylines. The examples include the SDK loader, while the application key remains an {appKey} placeholder. Coordinates, labels, colors, and other data values can be customized.

list_sdk_docs and get_sdk_doc cover Web JS SDK classes, methods, events, constructors, options, and value types. Documentation can be requested for a complete symbol or a method such as inavi.maps.Map#fitBounds.

Limitations and notes

The mapping material is scoped to South Korea. For a runnable page, start with a map example because the SDK loader is included there; SDK reference output alone is not a complete page. Verify undocumented options, methods, events, or styles through get_sdk_doc instead of relying on syntax from another map provider. A real application key must replace {appKey} before an example will run.