AMap Maps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_API_PORT | No | HTTP server port number (optional, default is 3000) | 3000 |
| HTTP_API_TOKEN | No | HTTP API access token (optional) | |
| AMAP_MAPS_API_KEY | Yes | AMap Maps API key (required) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| maps_regeocodeA | 将一个高德经纬度坐标转换为行政区划地址信息 |
| maps_geoA | 将详细的结构化地址转换为经纬度坐标。支持对地标性名胜景区、建筑物名称解析为经纬度坐标 |
| maps_ip_locationB | IP 定位根据用户输入的 IP 地址，定位 IP 的所在位置 |
| maps_weatherA | 根据城市名称或者标准adcode查询指定城市的天气 |
| maps_search_detailC | 查询关键词搜或者周边搜获取到的POI ID的详细信息 |
| maps_bicyclingA | 骑行路径规划用于规划骑行通勤方案，规划时会考虑天桥、单行线、封路等情况。最大支持 500km 的骑行路线规划 |
| maps_direction_walkingA | 步行路径规划 API 可以根据输入起点终点经纬度坐标规划100km 以内的步行通勤方案，并且返回通勤方案的数据 |
| maps_direction_drivingA | 驾车路径规划 API 可以根据用户起终点经纬度坐标规划以小客车、轿车通勤出行的方案，并且返回通勤方案的数据。 |
| maps_direction_transit_integratedA | 公交路径规划 API 可以根据用户起终点经纬度坐标规划综合各类公共（火车、公交、地铁）交通方式的通勤方案，并且返回通勤方案的数据，跨城场景下必须传起点城市与终点城市 |
| maps_distanceA | 距离测量 API 可以测量两个经纬度坐标之间的距离,支持驾车、步行以及球面距离测量 |
| maps_text_searchC | 关键词搜，根据用户传入关键词，搜索出相关的POI |
| maps_around_searchB | 周边搜，根据用户传入关键词以及坐标location，搜索出radius半径范围的POI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: POI search (text, around, detail), geocoding/reverse, path planning for four modes, distance, IP location, and weather. No overlap.
All tools follow the consistent pattern 'maps_<action>_<target>' in snake_case, e.g., maps_text_search, maps_direction_driving.
12 tools is appropriate for a map service, covering core functionality without unnecessary bloat.
The set covers essential map operations: POI search and details, geocoding/reverse, multi-modal route planning, distance, weather, and IP location. No obvious gaps.