Amazon Location Service MCP Server
Official AWS Labs MCP server for Amazon Location Service that gives AI assistants place search, geocoding, reverse geocoding, nearby and open-now search, and route calculation with waypoint optimization.
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Canonical URL
- https://heyclau.de/entry/mcp/aws-location-mcp-server
- Source URLs
- https://github.com/awslabs/mcp/blob/main/src/aws-location-mcp-server/README.md, https://github.com/awslabs/mcp, https://awslabs.github.io/mcp/
- Brand
- AWS Labs
- Brand domain
- aws.amazon.com
- Brand asset source
- brandfetch
- Safety notes
- This server calls Amazon Location Service place and route APIs with your AWS credentials; scope the profile to Location Service access and the intended account and region., The tools are query-oriented (search, geocode, route) rather than resource-mutating, but Amazon Location Service API calls may incur AWS usage costs., Run it only on a trusted host, since it uses the local machine's AWS credentials to reach your account.
- Privacy notes
- Place queries, coordinates, addresses, and waypoints you ask about are sent to Amazon Location Service using your configured credentials., Returned place details, addresses, and route geometry are exposed to the model; keep account identifiers and credentials out of public prompts, issues, and screenshots.
- Author
- AWS Labs
- Submitted by
- jaso0n0818
- Claim status
- unclaimed
- Last verified
- 2026-06-21
Safety notes
- This server calls Amazon Location Service place and route APIs with your AWS credentials; scope the profile to Location Service access and the intended account and region.
- The tools are query-oriented (search, geocode, route) rather than resource-mutating, but Amazon Location Service API calls may incur AWS usage costs.
- Run it only on a trusted host, since it uses the local machine's AWS credentials to reach your account.
Privacy notes
- Place queries, coordinates, addresses, and waypoints you ask about are sent to Amazon Location Service using your configured credentials.
- Returned place details, addresses, and route geometry are exposed to the model; keep account identifiers and credentials out of public prompts, issues, and screenshots.
Prerequisites
- An AWS account with Amazon Location Service enabled in your chosen region.
- Python 3.10 or newer and `uv` / `uvx` installed (Astral) to run the package.
- AWS credentials configured locally (for example via `aws configure` or `AWS_PROFILE`) with permissions for Amazon Location Service place and route APIs.
- An MCP client that supports stdio servers; the server runs locally on the same host as the client.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 10 minutes
- Difficulty
- intermediate
- Pricing
- open-source
- Disclosure
- editorial
- Application category
- DeveloperApplication
- Operating system
- Cross-platform
Full copyable content
{
"awslabs.aws-location-mcp-server": {
"command": "uvx",
"args": ["awslabs.aws-location-mcp-server@latest"],
"env": {
"AWS_PROFILE": "${AWS_PROFILE}",
"AWS_REGION": "us-east-1",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}About this resource
Overview
Amazon Location Service MCP Server is an official AWS Labs Model Context Protocol server that gives AI assistants access to Amazon Location Service. Instead of wiring up the Location Service SDK, Claude can search for places by name, geocode and reverse-geocode coordinates, find nearby or currently-open options, and calculate and optimize routes.
It runs locally over stdio via uvx from the published
awslabs.aws-location-mcp-server Python package and uses your local AWS
credentials, so scope those credentials to Amazon Location Service access.
Features
- Search for places — find places using geocoding from a text query.
- Get place details — look up details for a specific place by
PlaceId. - Reverse geocode — convert coordinates back into addresses.
- Search nearby — find places near a given location.
- Open-now search — find places that are currently open.
- Route calculation — calculate routes between locations.
- Optimize waypoints — reorder waypoints for an efficient route.
Use Cases
- Resolve an address or business into coordinates for a downstream task.
- Turn a set of coordinates into a human-readable address.
- Find nearby or currently-open options around a location.
- Plan and optimize a multi-stop route between waypoints.
Installation
Claude Code
- Install Python 3.10+ and
uv. - Configure an AWS profile and region with Amazon Location Service access.
- Add the server with the stdio configuration above (command
uvx, packageawslabs.aws-location-mcp-server@latest, envAWS_PROFILEandAWS_REGION). - Verify it is connected with
claude mcp list.
Claude Desktop / Cursor / Kiro / VS Code
Add the configSnippet above to your client's MCP configuration and set
AWS_PROFILE and AWS_REGION. The first run downloads the package via uvx.
Source And Trust
This entry is based on the official AWS Labs awslabs/mcp repository and the
published PyPI package (Apache-2.0). The server is query-oriented over Amazon
Location Service, but it uses your AWS credentials and incurs Location Service
usage, so scope permissions tightly and verify the configuration against the
linked source before using it in automated workflows.
Source citations
Add this badge to your README
How it compares
Amazon Location Service MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Official AWS Labs MCP server for Amazon Location Service that gives AI assistants place search, geocoding, reverse geocoding, nearby and open-now search, and route calculation with waypoint optimization. Open dossier | Official AWS Labs MCP server for Amazon ECS that helps AI assistants containerize applications, deploy them to ECS, troubleshoot deployments, and explore ECS and ECR resources across the container application lifecycle. Open dossier | Official AWS Labs MCP server for Amazon EKS that gives AI code assistants real-time cluster state visibility and Kubernetes/EKS resource management, from cluster setup through deployment, troubleshooting, and optimization. Open dossier | Official AWS Labs MCP server for Amazon SNS and SQS that lets AI assistants list and manage SNS topics, subscriptions, and SQS queues and send/receive messages, with resource tagging so it only modifies what it created. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | AWS Labs | AWS Labs | AWS Labs | AWS Labs |
| Added | 2026-06-21 | 2026-06-21 | 2026-06-21 | 2026-06-21 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓This server calls Amazon Location Service place and route APIs with your AWS credentials; scope the profile to Location Service access and the intended account and region. The tools are query-oriented (search, geocode, route) rather than resource-mutating, but Amazon Location Service API calls may incur AWS usage costs. Run it only on a trusted host, since it uses the local machine's AWS credentials to reach your account. | ✓The configuration above is read-only. Setting `ALLOW_WRITE=true` lets the server create and modify infrastructure (ECR repos, CloudFormation stacks, ECS services) and `ALLOW_SENSITIVE_DATA=true` exposes logs; enable these only deliberately. AWS documents this server as primarily for development, testing, and non-critical environments; keep write/sensitive-data disabled for production accounts and prefer non-production targets while evaluating it. This server acts on real infrastructure with your AWS credentials; scope the profile to the intended account, region, and resources, and run it only on a trusted host. | ✓The configuration above is read-only. Adding the `--allow-write` flag lets the server create, update, patch, and delete EKS/Kubernetes resources (including creating clusters via CloudFormation) and `--allow-sensitive-data-access` exposes logs and events; enable these only deliberately. This server acts on real infrastructure with your AWS credentials; scope the profile to the intended account, region, and clusters, and prefer non-production targets while evaluating it. Run it only on a trusted host, and review any generated manifests or CloudFormation actions before applying them. | ✓Resource creation/deletion is gated by the `--allow-resource-creation` flag (default off); without it, create/delete tools are hidden. Enable it only deliberately, and grant `AmazonSNSFullAccess`/`AmazonSQSFullAccess` only when you intend mutations. The server tags resources it creates and will only modify resources carrying that tag, which prevents it from changing pre-existing topics/queues it did not create. This server acts on real messaging infrastructure with your AWS credentials; scope the profile to the intended account and region and run it only on a trusted host. |
| Privacy notes | ✓Place queries, coordinates, addresses, and waypoints you ask about are sent to Amazon Location Service using your configured credentials. Returned place details, addresses, and route geometry are exposed to the model; keep account identifiers and credentials out of public prompts, issues, and screenshots. | ✓Cluster, service, task, task-definition, and ECR metadata plus account/region identifiers can be returned through tool calls and exposed to the model. With sensitive-data access enabled, logs and deployment details may be returned; keep account identifiers, credentials, and log contents out of public prompts, issues, and screenshots. | ✓Cluster state, resource manifests, ARNs, and account/region metadata can be returned through tool calls and exposed to the model. With sensitive-data access enabled, pod logs and Kubernetes events may be returned; keep account identifiers, credentials, and log contents out of public prompts, issues, and screenshots. | ✓Topic/queue names, ARNs, subscription details, and account/region metadata can be returned through tool calls and exposed to the model. Message send/receive tools can read and write message payloads; keep sensitive message contents, account identifiers, and credentials out of public prompts, issues, and screenshots. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related guides
Source-backed guides for putting this to work.
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.