Amazon Location Service vs TfL MCP Server
Amazon Location Service is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). TfL MCP Server is a plugin bundle for AI coding tools published by oneill9. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Amazon Location Service | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a84810ffd306 Forks (GitHub): 1 805 Pulls (Docker Hub): 13 406 Stars (Docker Hub): 0 Stars (GitHub): 9 776 Not marked · First seen |
Not listed |
| Community marketplace oneill9/mcp-server-tfl | Not listed | Listed Version: 2.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Amazon Location Service | TfL MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 776 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 13 406 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 805 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-location-mcp-server) | On your machine (@oneill9/tfl-mcp-server) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | Not a bundle | 7 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/oneill9/mcp-server-tfl |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Amazon Location Service
Place search, geocoding, and route optimization.
TfL MCP Server
Real-time London transport data — service status, arrivals, journey planning, fares, crowding, and bike points via the TfL Unified API.
How to run each
Amazon Location Service As a local MCP server: Docker image
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-location -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/aws-location-mcp-serverRequires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)
TfL MCP Server As a Codex plugin
codex plugin marketplace add oneill9/mcp-server-tflCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of TfL MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of TfL MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Amazon Location Service · What it can do: TfL MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.