This MCP server provides a suite of Amap (高德地图) related APIs via a modular MCP interface. It exposes tools for geocoding (maps_regeocode, maps_geo), location services (maps_ip_location, maps_weather), multiple route planning options (maps_bicycling_by_coordinates, maps_bicycling_by_address, maps_direction_walking_by_coordinates, maps_direction_walking_by_address, maps_direction_driving_by_coordinates, maps_direction_driving_by_address, maps_direction_transit_integrated_by_coordinates, maps_direction_transit_integrated_by_address), distance measurement (maps_distance), and POI search (maps_text_search, maps_around_search, maps_search_detail). Each tool accepts parameters as described in the README, such as coordinates, addresses, city names, or IDs, and returns structured results for downstream apps. To use the server, configure an MCP client to connect via one of the supported transports (stdio, SSE, or streamable-http) and provide the appropriate API key via the AMAP_MAPS_API_KEY environment variable. Typical usage involves starting the server with uvx amap-mcp-server and then pointing a client to the server or to the provided URL (e.g., SSE or streamable-http endpoints) depending on your deployment needs.

Prerequisites:

• Python 3.8+ installed on your system
• Access to PyPI (pip) to install the amap-mcp-server package

Install steps:

1. Create a virtual environment (recommended): python -m venv venv source venv/bin/activate # on Unix/macOS venv\Scripts\activate.bat # on Windows

2. Install the amap-mcp-server package from PyPI: pip install amap-mcp-server

3. Obtain an API key from the Amap (高德地图) Open Platform and set it as an environment variable when running the server: export AMAP_MAPS_API_KEY=your_api_key_here # Unix/macOS set AMAP_MAPS_API_KEY=your_api_key_here # Windows

4. Run the server using the recommended MCP transport (stdio by default via the UVX runner):

   StdIO (default) using uvx

   uvx amap-mcp-server

5. Verify the server starts correctly and note the available endpoints (SSE or Streamable HTTP can be used for remote deployments):

   SSE example (local): start the server with sse option and configure the MCP client accordingly

   uvx amap-mcp-server sse

6. See client configuration examples in the README to connect via your MCP client.

If you prefer a containerized or alternative setup, adapt the commands to your environment accordingly.

Notes and tips:

• The server requires an Amap API key accessible via the AMAP_MAPS_API_KEY environment variable.
• Supported MCP transport modes include stdio (default), SSE, and streamable-http. Choose based on deployment needs (local development vs. remote streaming).
• When using SSE, the MCP client should point to the provided SSE URL (e.g., http://0.0.0.0:8000/sse).
• When using Streamable HTTP, the MCP client should point to the /mcp endpoint (e.g., http://localhost:8000/mcp).
• Ensure network access to the Amap APIs and monitor for rate limits or quota issues.
• If you encounter authentication or API errors, double-check the API key scope and permissions in the Amap Open Platform console.
• The repository and README describe tool parameters in detail; provide the correct fields (locations, addresses, city names, etc.) when constructing MCP requests.