Why

LLMs are good at recommending places and itineraries, but bad at anything requiring real spatial understanding — distances, walkability, what's near what. This server closes that gap from both sides:

• The model checks its work. With a mapy.com API key, find_places turns names into real coordinates, so suggestions are grounded in actual places. show_places and show_route then return map images with numbered markers and a coordinate grid, so the model can see how the places relate before it answers — and a route comes with real distance, time and, on foot or by bike, an elevation profile.
• The user gets a map, not just text. Both tools hand the user a mapy.com link to the same places or route.

Built on mapy.com, the Czech mapping service from Seznam.cz — especially strong in the Czech Republic and the surrounding region.

Available tools

Links need no key. Map images, route planning and find_places call the mapy.com REST API, so they are only available when MAPY_API_KEY is set in the environment; without it, show_places and show_route return just the link.

Configuration

Set MAPY_API_KEY in the environment when you want map images, route planning and find_places. Get a free key from the mapy.com developer portal. With the key unset, the server still runs and returns mapy.com links.

// Example: Claude Desktop / Claude Code MCP config
{
  "mcpServers": {
    "mapy-com": {
      "command": "uvx",
      "args": ["mapy-com-mcp"],
      "env": { "MAPY_API_KEY": "your-key-here" }
    }
  }
}

License

MIT — see LICENSE.