iNavi Global Maps MCP Server

An MCP (Model Context Protocol) server that gives AI assistants map intelligence.

Connecting the iNavi Global Maps MCP Server lets an AI understand iNavi Global Maps' location-based APIs and build interactive maps directly. There's no need to read separate API documentation or hand-write boilerplate — you can implement map-based features just by describing what you want in natural language.

• API spec lookup - Provides the AI with iNavi Global Maps API specifications (search, route, and SDK) so it can write correct calling code
• Map visualization - Generates interactive maps from 17 HTML templates covering markers, clusters, polygons, and polylines

Good fit for:

• Rapid prototyping - Build map-based features through conversation with the AI instead of reading API docs
• Location-based service development - Build services around geocoding, route search, and address/POI search
• Data visualization - Visualize location data on an interactive map

Quick Start

Option 1: .mcpb Bundle (Claude Desktop only - recommended)

The easiest way to install. No environment setup required.

1. Download the latest .mcpb file from GitHub Releases
2. Drag and drop the downloaded .mcpb file onto Claude Desktop (or double-click it)
3. Restart Claude Desktop

Done! You can now ask Claude map-related questions.

Option 2: npx (any MCP host)

Works with Cursor, Windsurf, Claude Code, and other MCP hosts.

Prerequisite: Node.js 22 or later must be installed.

Config file location:

• Windows: %APPDATA%\Claude\claude_desktop_config.json
• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

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

Restart Claude Desktop after saving the config file.

Go to Cursor > Settings > Cursor Settings > Tools & MCP and add:

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

Run in your terminal:

claude mcp add inavi-maps-mcp npx -y @inavi-global-maps/mcp-server

Add the following to your editor's MCP config file:

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

Example Usage

After installing the MCP server, just ask the AI in natural language.

Explore APIs & Generate Code

This MCP server gives the AI iNavi Global Maps API specifications. The AI doesn't call the API itself — it references the spec to write correct calling code for you.

What geocoding-related APIs are available on iNavi Global Maps?

Show me the request/response spec for the reverse geocoding API

Write TypeScript code that calls the API to convert an address into coordinates

Create example code that calls the origin-to-destination route search API

Write code that loads the web map SDK JavaScript for a given app key

Map Visualization

The AI generates interactive map pages based on the HTML templates.

Create an HTML page that shows a marker on the map

Make a page that groups multiple points into clusters on the map

Visualize a route on the map with traffic-colored segments

Show several landmarks as polygon regions and markers on a map

Combining Both

Using API spec lookup and map visualization together enables more complex features.

Convert an address to coordinates with the geocoding API, then show the result as a marker on the map

Write code that visualizes the route search API's result as a polyline on the map

Available Tools

This MCP server provides 4 tools across two families, each designed as a discover → detail two-step workflow.

API Spec Tools

Provides the AI with iNavi Global Maps API specifications, so it can write correct API calling code without reading external documentation.

| Tool | Description | Key Input | |------|------|-----------| | list_api_specs | List API specs | category (optional) | | get_api_spec | Get detailed spec for a specific API | operationId (required) |

Workflow: Browse available APIs with list_api_specs, then pass an operationId to get_api_spec to get detailed parameters and request/response schemas.

| Category | Description | Included APIs | |---------|------|---------| | search | Search APIs that search and convert addresses, POIs, and coordinates (fuzzy search, geocoding, reverse geocoding) | Fuzzy Search, Geocoding, Reverse Geocoding | | route | Route search APIs | Standard Route Search | | sdk | Web/Mobile SDK APIs | Web Map JS Loader, Navi SDK Styles, Mobile Maps SDK Styles |

HTML Example Tools (Map Visualization)

Provides HTML templates for building interactive maps. The AI customizes the template's data values (coordinates, labels, etc.) to produce a tailored map page.

| Tool | Description | Key Input | |------|------|-----------| | list_map_examples | List available map examples | category (optional) | | get_map_example | Get a specific map example's HTML | id (required) |

Workflow: Browse available examples with list_map_examples, then pass an id to get_map_example to get the complete HTML code.

| Category | Count | Included Examples | |---------|--------|----------| | dynamic-maps | 4 | Basic map, map info display, distance calculation, FlyTo animation | | marker | 6 | Basic marker, movable marker, clustering, cluster grid size, numbered markers, colored markers | | infowindow | 2 | Basic InfoWindow, InfoWindow with clustered markers | | shapes | 5 | Circle, polygon, multi-polygon, dynamic styling, polyline (traffic colors) |

Troubleshooting

MCP server won't connect

1. Check your Node.js version: Node.js 22 or later is required (check with node -v)
2. Restart the MCP host: Always restart after changing configuration
3. Check the config file: Make sure there are no JSON syntax errors

JSON parsing errors

Unexpected token...is not valid JSON

Fix:

• Update to the latest version (this was a known, since-fixed issue)
• During local development, use MCP logging instead of console.log (avoids polluting stdout)

License

MIT License - free to use, modify, and distribute. See the LICENSE file for details.

References

• Model Context Protocol - Official MCP documentation
• Claude Desktop - Download Claude Desktop
• iNavi Global Maps API - Official iNavi Global Maps API documentation