Vinkius
TfL logo
Vinkius
Vinkius runs on AutoGen

How to Use the TfL MCP in AutoGen

Run consensus-driven decision making with AutoGen over TfL data.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

TfL MCP on Cursor AI Code Editor MCP Client TfL MCP on Claude Desktop App MCP Integration TfL MCP on OpenAI Agents SDK MCP Compatible TfL MCP on Visual Studio Code MCP Extension Client TfL MCP on GitHub Copilot AI Agent MCP Integration TfL MCP on Google Gemini AI MCP Integration TfL MCP on Lovable AI Development MCP Client TfL MCP on Mistral AI Agents MCP Compatible TfL MCP on Amazon AWS Bedrock MCP Support
MCP Servers — Included with Plan
Vinkius runs on AutoGen

Connect TfL MCP to AutoGen

Create your Vinkius account to connect TfL to AutoGen — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Key Capabilities

Debating Optimal Journeys

You can set up a multi-agent system where one agent uses `get_journey` to suggest the fastest path, and another challenges that suggestion using `get_road_disruptions`. They debate whether the time savings are worth the risk of localized road incidents. The final decision is not just the 'best' answer; it’s the consensus reached after competing perspectives argue over the data.

Cross-Checking Service Reliability

A Performance Agent might call `get_arrivals` to confirm immediate service times. Meanwhile, a Safety Agent calls `get_line_status` to check for systemic issues like 'Part Suspended.' The agents must then reconcile these two conflicting data points (real-time vs. macro status) before giving the user an answer. This simulates human deliberation when the source data is ambiguous.

Vetting Vehicle Compliance

One agent checks if a vehicle registration is ULEZ compliant using `get_vehicle_details`. A second, 'Logistics' agent then uses `get_road_disruptions` to determine if the specific route segment has any temporary weight or size restrictions. They debate if the initial compliance check even matters given the roadworks. It forces a complex vetting process over simple API lookups.

Setup guide

Set up TfL MCP in AutoGen

Prerequisites

  • Python 3.10+ installed
  • autogen-ext[mcp] package
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install AutoGen with MCP

    Run pip install "autogen-ext[mcp]" autogen-agentchat. The MCP extension includes mcp_server_tools for stateless tool access.

  2. 2

    Fetch tools from the MCP

    Call mcp_server_tools(SseServerParams(url=...)) with your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

  3. 3

    Run your agent

    Pass the tools to AssistantAgent and call agent.run(). The agent invokes TfL tools and returns structured results.

agent.py
from autogen_ext.tools.mcp import SseServerParams, mcp_server_tools
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

tools = await mcp_server_tools(server_params)

agent = AssistantAgent(
    name="TfL_assistant",
    model_client=OpenAIChatCompletionClient(model="gpt-4o"),
    tools=tools,
)

result = await agent.run("List recent TfL data")
print(result.messages[-1].content)

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about TfL MCP in AutoGen

The agents start by calling `get_journey` for initial plans. Then, one agent might challenge the plan by running `get_place_search` to see if a better-located stop exists, leading to a revised route consensus.
Absolutely. You can assign an 'Operations' agent the task of calling `get_line_status`. This agent reports back on severity (e.g., Minor Delays) and disruption details, which other agents then build their recommendations around.
An 'Optimization' agent uses `get_bike_points` to find available docks. A second agent confirms the location and accessibility using `get_stop_point_details`. They debate whether the dock is convenient enough for the user.
You'll build a 'Verification' agent whose only job is to cross-reference `get_road_disruptions` against any proposed route. This makes the system highly skeptical and forces it to acknowledge potential closures.
The server touches public infrastructure data, including vehicle registrations (`get_vehicle_details`), stop point coordinates, and operational status. The agents only process these non-personal system metrics.

Start using the TfL MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 12 tools

We've already built the connector for TfL. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.