Map Parser vs INAVI Maps API
Map Parser is an MCP server published by changzhiai. Marketplaces we read that list it: 1 (Official MCP Registry). INAVI Maps API is an MCP server published by inavi-systems. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Map Parser |  INAVI Maps API |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.5 No figure published Not marked · First seen |
Listed Version: 0.0.4 Downloads/month (npm): 774 Downloads/week (npm): 95 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Map Parser | INAVI Maps API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mapparser.travel-tracker.org/mcp) | On your machine (@inavi-maps/api-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/inavi-systems/inavi-api-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-30 | 2026-10-23 |
| Endpoint at the last check (differs) | Responded 19 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Map Parser
Parse Google Maps links into stops with coordinates. Geocode, route, and export.
INAVI Maps API
INAVI Maps API for AI (South Korea): place search, geocoding, routes on an interactive map
How to run each
Map Parser As a remote MCP server
claude mcp add --transport http map-parser https://mapparser.travel-tracker.org/mcpINAVI Maps API As a local MCP server: npm package
claude mcp add --env "INAVI_APPKEY=<YOUR_INAVI_APPKEY>" --transport stdio inavi-api-mcp -- npx -y @inavi-maps/api-mcp-serverRequires: INAVI_APPKEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Map Parser has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Map Parser publish no settings it asks for, so we do not compare settings.
What it can do: Map Parser · What it can do: INAVI Maps API · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.