2,500+ MCP servers ready to use
Vinkius

Transport for London MCP Server for CrewAI 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Transport for London through the Vinkius — pass the Edge URL in the `mcps` parameter and every Transport for London tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Transport for London Specialist",
    goal="Help users interact with Transport for London effectively",
    backstory=(
        "You are an expert at leveraging Transport for London 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 Transport for London "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Transport for London
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 Transport for London MCP Server

Connect to Transport for London (TfL) and access real-time London transit data through natural conversation — no API key needed.

When paired with CrewAI, Transport for London becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Transport for London tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

  • Tube Status — Check real-time status of all Underground lines (Good Service, Minor/Severe Delays, Suspended)
  • Line Details — Get detailed info about any tube, overground, DLR, Elizabeth line or tram route
  • Bus Arrivals — Get live bus arrival predictions for any stop
  • Journey Planning — Plan journeys between any two London locations with step-by-step directions
  • Road Status — Check major road status and disruptions across London
  • Bike Points — Find Santander Cycle docking stations with bike and dock availability
  • Stop Search — Search for bus stops, tube stations and river piers by name

The Transport for London MCP Server exposes 11 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 Transport for London to CrewAI via MCP

Follow these steps to integrate the Transport for London MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py — CrewAI auto-discovers 11 tools from Transport for London

Why Use CrewAI with the Transport for London MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Transport for London through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Transport for London + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Transport for London MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Transport for London for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Transport for London, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Transport for London tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Transport for London against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Transport for London MCP Tools for CrewAI (11)

These 11 tools become available when you connect Transport for London to CrewAI via MCP:

01

get_arrivals

Returns predicted arrival times, destination, line number, vehicle ID and expected time to station. Use the stop point ID (e.g. "490009056W") from search_stop. Get live arrival predictions for a bus stop

02

get_bike_point_detail

Get detailed info for a specific bike docking station

03

get_bike_points

Returns bike availability, dock availability, station locations and status. Useful for finding nearby bikes for cycling journeys. Search for Santander Cycle (Boris Bike) docking stations

04

get_journey

Returns multiple route options with estimated duration, walking distance, fare cost, number of changes and step-by-step directions. Input locations can be station names, addresses or postcodes. Plan a journey between two points in London

05

get_line_detail

Supports tube, overground, DLR, Elizabeth line, tram and river bus lines. Get detailed information about a specific TfL line

06

get_line_routes

Returns the ordered list of stations the line serves. Useful for understanding the full journey path of a tube line. Get the route sequence for a TfL line

07

get_line_status

Shows whether each line has Good Service, Minor Delays, Severe Delays, or is Suspended/Part Suspended. If no line IDs specified, returns all tube lines. Use line_ids to check specific lines (comma-separated, e.g. "central,victoria,northern"). Get real-time status for TfL tube lines

08

get_road_disruptions

Returns disruption details with severity, location, cause and estimated clearance times. Get current road disruptions in London

09

get_road_status

Shows whether roads have Good, Minor or Severe congestion. Get status of London major roads

10

get_stop_details

Useful for identifying the correct stop ID for arrival queries. Get details for a specific bus stop or station

11

search_stop

Returns matching stops with their IDs, locations, modes and routes. Use the returned IDs with get_arrivals or get_stop_details. Search for bus stops and stations by name

Example Prompts for Transport for London in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Transport for London immediately.

01

"What's the status of the Central line?"

02

"Plan a journey from King's Cross to Heathrow."

03

"When is the next bus at Oxford Circus?"

Troubleshooting Transport for London MCP Server with CrewAI

Common issues when connecting Transport for London to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Transport for London + CrewAI FAQ

Common questions about integrating Transport for London MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own 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.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Connect Transport for London to CrewAI

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.