MCP server registry
Physical & geospatialPublic source

Maps & Geolocation MCP Server

Geolocation and routing for ADK-Rust Enterprise agents. Provides 7 MCP tools for geocoding, routing, elevation, POI search, and distance matrices — zero configuration, no API keys, powered by OpenStreetMap.

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

Zero configuration — works out of the box with no API keys or environment variables.

02

Global coverage — OpenStreetMap data covers every country on Earth.

03

Multiple transport modes — driving, walking, and cycling routes.

04

Turn-by-turn directions — full step-by-step navigation instructions.

05

POI discovery — find hospitals, restaurants, ATMs, and more near any point.

06

Registry-ready — ships with mcp-server.toml for automatic ADK-Rust Enterprise onboarding.

Architecture

How Maps & Geolocation MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Maps & Geolocation MCP Server

Validates the request and owns 7 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

From the project documentation

The server’s published architecture

Open the source diagram ↗
Maps & Geolocation MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Maps & Geolocation MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

7 named tools

geocode

Geocode address to coordinates

read only
reverse_geocode

Reverse geocode coordinates to address

read only
get_route

Calculate route with directions

read only
get_elevation

Get elevation for coordinates

read only
search_poi

Search points of interest nearby

read only
distance_matrix

Distance matrix between multiple points

read only
get_timezone

Get timezone/country for coordinates

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

7 read only
  • The registry manifest declares read only tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install mcp-maps
MCP client configuration
{
  "mcpServers": {
    "maps": { "command": "mcp-maps" }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.0.0
License
Apache-2.0
Tools
7
Revision
04447c5fa4ab
Updated
May 27, 2026
Transportsstdio