Tfl Mcp Server

Name: Tfl Mcp Server
Author: oneill9

by oneill9communityv1.5.1

An MCP server that exposes the TfL Unified API to AI assistants for querying live London transport data. It can return service status, live arrivals, journey plans, Santander Cycle docking stations, crowding levels, and fare information.

From the registry: Community-built server providing real-time London transport data via the TfL Unified API

GitHub Repository

Install & configure

Prerequisites

required
Install Node.js
Node.js is required to run the recommended NPX-based server launch command.
https://nodejs.org/
required
Get a TfL API key
Register a free TfL API key. The README says this is strongly recommended because TfL applies strict rate limits without a key, which impacts most real-world usage.
https://api-portal.tfl.gov.uk/

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `tfl-mcp-server` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js** — Node.js is required to run the recommended NPX-based server launch command. (https://nodejs.org/)
- **Get a TfL API key** — Register a free TfL API key. The README says this is strongly recommended because TfL applies strict rate limits without a key, which impacts most real-world usage. (https://api-portal.tfl.gov.uk/)

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@oneill9/tfl-mcp-server"]
- required environment variables:
  - `TFL_APP_KEY`: TfL API key. Strongly recommended and effectively required for practical use because default unauthenticated usage is heavily rate-limited. (example: `<your-tfl-api-key>`)
- optional environment variables:
  - `TFL_APP_ID`: TfL App ID. Only needed for older TfL API registrations that issued both an app ID and key. (example: `<your-tfl-app-id>`)

Note: The README also documents a Docker stdio launch path, but the NPX path is the simplest and most portable, so it is preferred. Although the project mentions a Java implementation with HTTP/SSE support, the README’s canonical install instructions for this package are stdio-based and do not provide a direct canonical HTTP/SSE config shape here.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README also documents a Docker stdio launch path, but the NPX path is the simplest and most portable, so it is preferred. Although the project mentions a Java implementation with HTTP/SSE support, the README’s canonical install instructions for this package are stdio-based and do not provide a direct canonical HTTP/SSE config shape here.