London Transport Mcp Server

Created By
anoopt8 months ago
Overview

What is London Transport MCP Server?

The London Transport MCP Server is an independent project that provides real-time transport data from Transport for London (TfL) using the publicly available TfL Unified API. It offers functionalities such as line status updates, journey planning, and disruption information.

How to use London Transport MCP Server?

Users can connect to the server using compatible clients like Claude Desktop or VS Code. Configuration settings are provided for easy integration, and a public demo instance is available for testing without deployment.

Key features of London Transport MCP Server?

  • Get Line Status: Retrieve the current status of specific TfL transport lines.
  • Plan Journey: Plan journeys between two locations in London with various customizable parameters.
  • Public Demo: Test the server without needing to deploy it yourself.
  • API Key Support: Optional authentication for higher rate limits and better performance.

Use cases of London Transport MCP Server?

  1. Checking the operational status of the Northern line.
  2. Planning a journey from King's Cross to Heathrow Airport.
  3. Finding the fastest route from Wimbledon to Liverpool Street.

FAQ from London Transport MCP Server?

  • Is this an official TfL service?

No, this is an independent project and is not officially affiliated with TfL.

  • Do I need an API key to use the server?

No, but using an API key is recommended for better performance and higher rate limits.

  • How can I deploy the server?

You can deploy it easily to Cloudflare Workers with a single click or manually by cloning the repository.

Server Config

{
  "mcpServers": {
    "tfl": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://london-transport-mcp.anoopt.workers.dev/mcp"
      ]
    }
  }
}
Project Info
Created At
8 months ago
Updated At
7 months ago
Author Name
anoopt
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago