TfL MCP Server for CrewAI 12 tools — connect in under 2 minutes
Connect your CrewAI agents to TfL through Vinkius, pass the Edge URL in the `mcps` parameter and every TfL tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="TfL Specialist",
goal="Help users interact with TfL effectively",
backstory=(
"You are an expert at leveraging TfL tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in TfL "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 12 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About TfL MCP Server
Connect your TfL Unified API London public transport data platform to any AI agent and take full control of real-time Tube and bus tracking, multimodal journey planning, line status monitoring, and Santander Cycles availability through natural conversation.
When paired with CrewAI, TfL becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TfL tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
What you can do
- Real-Time Arrivals — Get live arrival predictions for any Tube station, bus stop, DLR, Overground, Elizabeth line, tram, river, or cable-car stop
- Stop Point Search — Find any TfL stop point by station name, street, or landmark across all transport modes
- Line Status — Check current service status for all Tube lines, bus routes, DLR, Overground, Elizabeth line, and more
- Journey Planning — Plan door-to-door multimodal trips combining Tube, bus, DLR, Overground, Elizabeth line, tram, walking, and cycling
- Stop Details — Get comprehensive station information including accessibility, fare zones, and step-free access
- Santander Cycles — Browse all bike docking stations with real-time availability (bikes and empty docks)
- Road Status — Monitor London road conditions, closures, and disruptions for driving planning
- Place Search — Discover places and points of interest across London by category
- Transport Modes — Explore all available transport modes in the TfL network
- Vehicle Compliance — Check ULEZ and Congestion Charge compliance for registered vehicles
The TfL MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect TfL to CrewAI via MCP
Follow these steps to integrate the TfL MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 12 tools from TfL
Why Use CrewAI with the TfL MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with TfL through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
TfL + CrewAI Use Cases
Practical scenarios where CrewAI combined with the TfL MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries TfL for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries TfL, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain TfL tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries TfL against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
TfL MCP Tools for CrewAI (12)
These 12 tools become available when you connect TfL to CrewAI via MCP:
get_arrivals
g., 940GZZLUSCL for Oxford Circus Underground, or 490007653 for a bus stop). Returns predicted arrival times, line names, destination stations, time to station in minutes, vehicle IDs, expected arrival timestamps, and service types (tube, bus, dlr, elizabeth-line, overground, tram, river, cable-car). Essential for real-time arrival awareness, passenger waiting time estimation, trip timing, and connection coordination across the entire London transport network. AI agents should reference this when users ask "when is the next Northern Line train at Bank", "show upcoming buses at stop 490007653", or need real-time arrival predictions for any TfL stop point. Stop IDs can be found using search_stop_point. Get real-time arrival predictions for a specific TfL stop point
get_bike_point
Returns dock ID, common name, precise location (latitude, longitude, address), total capacity, current available bikes, current empty docks, installation date, last update timestamp, and operational status. Essential for dock-level bike availability checks, capacity planning, and real-time bike-sharing awareness for specific docking stations. AI agents should use this when users ask "how many bikes are at dock BikePoints_1234", "tell me about the docking station at Hyde Park Corner", or need specific docking station details for bike hire planning. Get detailed information about a specific Santander Cycles docking station
get_bike_points
Returns docking station IDs, common names, geographic coordinates, total bike capacity, number of available bikes, number of empty docks, installation date, and operational status. Covers thousands of docking stations across central London and expanding into outer boroughs. Essential for bike hire planning, dock availability awareness, cycle route planning, and understanding London's bike-sharing network coverage. AI agents should reference this when users ask "where are the nearest bike docking stations", "how many bikes are available at this dock", or need to identify bike hire options for last-mile connectivity. List all Santander Cycles (bike hire) docking stations across London
get_journey
Returns multiple route options combining tube, bus, dlr, overground, elizabeth-line, tram, river, walking, and cycling. Each route includes total duration, walking distance, number of interchanges, fare estimates, CO2 savings, and detailed leg-by-leg instructions with line names, directions, station sequences, and departure/arrival times. Essential for multimodal trip planning, route comparison, accessibility-aware journey selection, and passenger information. AI agents should use this when users ask "how do I get from Paddington to Greenwich", "plan a journey from Heathrow to Tower Bridge", or need door-to-door trip planning across London's transport network. Plan a journey between two locations using TfL transport modes
get_line_status
Returns line IDs, line names, status severity (Good Service, Minor Delays, Severe Delays, Part Suspended, Suspended, Planned Work, Special Service), status descriptions, reason codes, and disruption details. Can query all lines system-wide or filter by specific modes (tube, bus, dlr, overground, tram, river, cable-car, elizabeth-line, national-rail). Essential for service disruption awareness, alternative route planning, passenger communication, and understanding overall TfL reliability. AI agents should reference this when users ask "is the Victoria Line running normally", "what is the status of the Overground", or need to check service reliability before planning London journeys. Get current service status for TfL lines, optionally filtered by mode
get_modes
Returns modes including tube, bus, dlr, overground, elizabeth-line, tram, river, cable-car, national-rail, and walking. Essential for understanding the scope of TfL's multimodal network, mode identification for filtered queries, and transport network analysis. AI agents should reference this when users ask "what transport modes does TfL cover", "list all available modes", or need to understand the full range of London transport options before planning journeys. List all available transport modes in the TfL network
get_place_search
Returns place IDs, names, categories, geographic coordinates, address information, and related links. Can optionally filter by place type (e.g., "TubeStation", "BusStation", "Park", "Museum", "Hospital"). Essential for place discovery, tourist planning, accessibility research, and understanding London's infrastructure. AI agents should use this when users ask "find parks near Westminster", "search for museums in South Bank", or need to identify places and points of interest for comprehensive London trip planning. Search for places and points of interest across London
get_road_disruptions
Returns disruption descriptions, affected road segments, cause types (roadworks, incidents, events, utility works), start and end dates, severity levels, and alternative route recommendations. Can query all disruptions system-wide or filter by specific road. Essential for driving disruption awareness, alternative route planning, delivery logistics, and understanding road reliability. AI agents should reference this when users ask "are there any roadworks on the A4", "what disruptions affect my drive to Heathrow", or need to check road conditions before planning driving journeys in London. Get current road disruptions and closures across London
get_road_status
Returns road IDs, road names, status descriptions, corridor details, and operational information. Can query all roads system-wide or filter by a specific road ID (e.g., "A1", "A40", "A205" South Circular). Essential for driving route planning, road closure awareness, understanding London road network conditions, and commuter driving decisions. AI agents should use this when users ask "what is the status of the A40", "are there any road closures on the North Circular", or need to check road conditions before driving journeys in London. Get current status of London roads, optionally filtered by specific road
get_stop_point_details
Returns stop ID, common name, station type, modes served, geographic coordinates, address, accessibility information (step-free access, lift availability), fare zone, hub station affiliations, and parent/child station relationships. Essential for stop identification, accessibility planning, fare zone awareness, station navigation, and understanding station hierarchy in the TfL network. AI agents should use this when users ask "tell me about King's Cross station", "is this station step-free", or need detailed stop metadata to contextualise transit queries. Get detailed information about a specific TfL stop point
get_vehicle_details
Returns vehicle registration, make, model, compliance status, charge exemptions, and registration dates. Essential for London driving compliance checks, ULEZ awareness, congestion charge planning, and vehicle registration verification. AI agents should use this when users ask "check if vehicle AB12 CDE is ULEZ compliant", "is my car exempt from Congestion Charge", or need to verify vehicle compliance before driving in central London. Get vehicle details for a registered vehicle in London (ULEZ/congestion charge)
search_stop_point
Returns matching stop points with their IDs, common names, modes served (tube, bus, dlr, overground, tram, river, cable-car, elizabeth-line), geographic coordinates (lat/lon), and station hierarchy information. Can optionally filter by transport mode. Essential for stop discovery, journey planning interfaces, stop identification, and building location-based transit features. AI agents should use this when users ask "find the tube station near Covent Garden", "search for stops called Victoria", or need to identify stop IDs for use in arrival queries. Search for TfL stop points by name or location
Example Prompts for TfL in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with TfL immediately.
"When is the next Northern Line train arriving at Bank station?"
"How many Santander Cycles are available near Hyde Park Corner?"
"What is the status of the Victoria Line and Jubilee Line right now?"
Troubleshooting TfL MCP Server with CrewAI
Common issues when connecting TfL to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
TfL + CrewAI FAQ
Common questions about integrating TfL MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect TfL with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect TfL to CrewAI
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.