Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Community-built server providing real-time London transport data via the TfL Unified API
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TFL_APP_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tfl": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TFL_APP_KEY",
"ghcr.io/oneill9/mcp-server-tfl:1.4.0"
],
"env": {
"TFL_APP_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add tfl --env TFL_APP_KEY=your-value -- docker run -i --rm -e TFL_APP_KEY ghcr.io/oneill9/mcp-server-tfl:1.4.0Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tfl": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TFL_APP_KEY",
"ghcr.io/oneill9/mcp-server-tfl:1.4.0"
],
"env": {
"TFL_APP_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tfl": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TFL_APP_KEY",
"ghcr.io/oneill9/mcp-server-tfl:1.4.0"
],
"env": {
"TFL_APP_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account oneill9, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TFL_APP_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.4.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Disclaimer: This is a community-built project. It is not affiliated with, endorsed by, or connected to Transport for London (TfL). This project consumes the publicly available TfL Unified API.
An MCP server that exposes the TfL (Transport for London) Unified API as tools, allowing AI assistants like Claude to query live London transport data.
Version 2 is a single Node.js 22 implementation using the MCP 2026-07-28 protocol revision. It supports stdio for local hosts, npm, and MCPB, plus stateless Streamable HTTP at /mcp for remote deployments.
Protocol compatibility: Streamable HTTP is modern-only MCP
2026-07-28. The stdio entry point also accepts 2025-era initialization for desktop hosts such as Codex, while modern stdio clients continue to negotiate2026-07-28. Legacy HTTP/SSE is not supported.
Step 1 — Add to Claude Desktop
Open your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonOption A: Node.js MCPB (recommended)
Download tfl-mcp-server.mcpb from GitHub Releases and install it in Claude Desktop.
Option B: npm
With Node.js 22 or later installed, point Claude Desktop at the published package:
{
"mcpServers": { "tfl-mcp-server": { "command": "npx", "args": ["-y", "@oneill9/tfl-mcp-server@2.0.0"], "env": { "TFL_APP_KEY": "your_key_here" } } } }
Option C: Docker
{
"mcpServers": { "tfl-mcp-server": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "TFL_APP_KEY", "ghcr.io/oneill9/tfl-mcp-server:latest"] } } }
Step 2 — Add a TfL API key (recommended)
Without a key, TfL applies strict rate limits that will impact most real-world usage. Register a free key and pass it via the TFL_APP_KEY environment variable. The Docker example's -e TFL_APP_KEY forwards this value into the container:
"env": { "TFL_APP_KEY": "your_key_here" }
Step 3 — Restart Claude Desktop and start asking questions
Example: *"Is the Central line running normally?"*, *"When is the next bus from Oxford Circus?"*
For source, Docker, and Streamable HTTP options, see docs/installation.md.
| Tool | Description | TfL Endpoint |
|---|---|---|
service_status | Current status and disruptions by mode | GET /Line/Mode/{modes}/Status |
arrivals | Live arrivals at a stop by name | GET /StopPoint/{naptan}/Arrivals |
journey | Plan a journey between two points | GET /Journey/JourneyResults/{from}/to/{to} |
bike_points | List Santander Cycles docking stations | GET /BikePoint |
crowding | Live station crowding level by name | GET /Crowding/{naptan}/Live |
fares | Fare information between two named stops | GET /StopPoint/{id}/FareTo/{targetId} |
Note: The server uses the
/StopPoint/Search/{query}endpoint internally to automatically resolve stop names to NaPTAN IDs for thearrivals,crowding, andfarestools.
The service_status tool includes MCP Apps support as a progressive enhancement. UI-capable hosts (e.g. Claude Desktop) can render an interactive service status board alongside the text response. Non-UI hosts continue to receive the standard text output.
See docs/tools.md for full details.
The MCPB and default container mode use stdio transport. The optional Streamable HTTP mode does not implement OAuth or any other server-side authentication; deploy it only behind an appropriate trusted access layer.
The TfL API uses a simple API key (TFL_APP_KEY) that you supply as an environment variable. A key is strongly recommended — without one, TfL applies strict rate limits that will impact most real-world usage. Registration is free. No OAuth flow, login, or account beyond the TfL portal is required to use this MCP server.
| Environment Variable | Default | Description |
|---|---|---|
TFL_APP_KEY | *(none)* | TfL API key — register at api-portal.tfl.gov.uk |
TFL_APP_ID | *(none)* | TfL App ID — only needed for older API registrations that issued both an ID and key |
MCP_MAX_REQUEST_BODY_BYTES | 1048576 | Maximum JSON request body size accepted by Streamable HTTP |
MCP_REQUEST_TIMEOUT_MS | 30000 | Streamable HTTP request timeout in milliseconds |
MCP_HEADERS_TIMEOUT_MS | 10000 | Streamable HTTP header timeout in milliseconds; must not exceed the request timeout |
An API key is strongly recommended — without one, TfL's strict rate limits will impact most real-world usage. Registration is free at api-portal.tfl.gov.uk.
Node.js 22 or later is required. Install from the lockfile and build before starting the server.
cd node
npm ci npm run build node dist/index.js
That starts stdio transport. For stateless Streamable HTTP:
cd node
HOST=127.0.0.1 PORT=8080 node dist/index.js --http
Connect an MCP 2026-07-28 client to http://127.0.0.1:8080/mcp. Set MCP_ALLOWED_HOSTS to a comma-separated hostname allowlist when serving under other hostnames.
For use with Claude Desktop, see docs/installation.md.
Unit tests use a mock HTTP server — no network access or API key required:
cd node && npm test
The Streamable HTTP acceptance tests are included in npm test. Run the official frozen MCP 2026-07-28 requirement set separately (optional extension probes outside that set are not scored):
cd node && npm run test:conformance
The conformance fixture registers the real production TfL tools and resource through the shared modern-only HTTP adapter. It also adds test-only diagnostic tools, resources, prompts, and flows needed by the referee's hard-coded probes; those diagnostics are not exposed by the production entry point.
Contract tests call the live TfL API:
cd node && TFL_APP_KEY=your_key_here npm run contractTest
Build and smoke-test the packed npm CLI, MCPB, and container distributions with bash scripts/test-distributions.sh. The script skips container checks when Docker is unavailable.
For questions, bug reports, or feature requests, please open an issue on GitHub Issues.
This MCP server acts as a local proxy between your AI assistant and the TfL Unified API. It does not collect, store, or transmit any personal data beyond what is required to forward your queries to TfL.
api.tfl.gov.uk). See TfL's privacy policy for how TfL handles API usage data.The full privacy policy is available at PRIVACY.md.
This server has been reviewed for compliance with the Anthropic Software Directory Terms and Anthropic Software Directory Policy. See COMPLIANCE.md for the full compliance statement and maintainer commitments.