An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect London Traffic Flows Licensed Vehicles Co to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Pull official London transport datasets directly into your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 8 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through London Datastore.

  1. 01

    Congestion charge monthly

    This capability provides monthly TfL congestion-charge enforcement activity. You can filter by specific months or use paging to navigate the records.

  2. 02

    Congestion charge overview

    This capability returns congestion-charge enforcement totals for each charging year. It includes the month with the highest number of confirmed vehicles.

  3. 03

    Licensed vehicle lookup

    This capability retrieves DVLA licensed-vehicle counts for a specific local authority. You just need to provide the name of the borough.

  4. 04

    Licensed vehicles

    This capability pulls vehicle counts licensed to London local authorities between 2019 and 2022. You can specify a year and a borough to get the data.

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through London Datastore.

  1. 05

    Traffic flow lookup

    This capability accesses a full 33-year series of traffic-flow data for a single local authority. It covers the period from 1993 to 2025.

  2. 06

    Traffic flows

    This capability provides average daily road-traffic flows for the 33 London boroughs and various aggregate regions. You can filter by a specific calendar year.

  3. 07

    Traffic flows ranking

    This capability ranks local authorities based on their average daily traffic flow for a given year. You can request a top-N list of the busiest areas.

  4. 08

    Traffic overview

    This capability provides headline numbers across all London traffic datasets. It serves as a quick way to get recent flows, vehicle counts, and congestion charge data in one call.

Real work

What teams actually run

01

Historical Trend Analysis

Compare traffic volumes in a specific borough from 1993 to 2025 to see long-term shifts.

02

Congestion Impact Studies

Analyze monthly camera captures in the congestion charge zone to track enforcement activity.

03

Fleet Composition Research

Check the split between private and company plate vehicles in different boroughs using licensed vehicle data.

04

Borough Benchmarking

Rank London authorities by daily traffic flow to identify the most congested areas.

One connector, every AI

London Datastore works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put London Datastore to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1656ms average. Fast in production.

London Datastore is checked daily against the live service.

Daily averagePeak 1875ms
Sep 28Today
Fastest day
1542ms
Slowest day
1875ms
14-day trend
Stable+4%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of London Datastore, so you can see the experience inside your AI.

It does not authenticate your account with London Datastore. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

London Datastore Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_bDM1cNIqLX2MjhBGK3XujpgRKZD3TR71iUaIVqWu/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — London Datastore capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "london-traffic-flows-licensed-vehicles-congestion-charge-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_bDM1cNIqLX2MjhBGK3XujpgRKZD3TR71iUaIVqWu/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up London Datastore in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work London Datastore owners hand off.

This MCP is built for professionals who need to query official London transport statistics without manual data extraction.

  • 01

    Transport Planners

    They ask the agent to pull historical traffic flows to inform infrastructure decisions.

  • 02

    Mobility Journalists

    They use the capability to find specific vehicle counts or congestion trends for reporting.

  • 03

    Data Analysts

    They query borough-level vehicle licensing and traffic rankings to build benchmarks.

FAQ

Questions London Datastore owners ask.

  • 01

    Where does this data come from?

    All data is sourced directly from the official London open-data platform (data.london.gov.uk).

  • 02

    How far back does the traffic data go?

    The traffic flow datasets provide annual vehicle flows for London boroughs from 1993 through 2025.

  • 03

    Can I see data for specific boroughs?

    Yes, most capabilities allow you to specify a local authority (la) to get data for a specific borough.

  • 04

    What is a charging year for the congestion charge?

    Charging years run from July to the following June. For example, the 2024/25 year covers July 2024 through June 2025.

  • 05

    Does this include all types of vehicles?

    The traffic flow capabilities allow you to specify if you want data for cars only or for all vehicles, including buses and HGVs.

  • 06

    Do I need an API key?

    No. data.london.gov.uk publishes every dataset as an anonymous file download (CSV or Excel). This MCP defines no credentials and needs nothing configured.

  • 07

    "Cars" vs "all vehicles". what is the difference?

    The flow table has two cuts of the same counts: the cars-only series and the all-vehicles series (cars plus buses, HGVs and everything else). Pick the vehicle_type that matches your question; the ranking and lookup capabilities honour the same choice.

  • 08

    What is a "charging year"?

    The congestion charge runs Jul 2010 through Jul 2026 in the dataset. A charging year bundles one July to the next June: Jul-10 to Jun-11 is the 2010/11 charging year, and so on. congestion_charge_overview groups the monthly rows by that label and reports the busiest month of each.

  • 09

    Where do the vehicle-flow counts come from?

    Annual road counts on each borough's major roads, published by the city, 1993 through 2025. The table rows are the 33 boroughs, a London aggregate and a Great Britain row; trailing empty rows in the source file are dropped by the capabilities.

Explore

More in Government Public Data

Suggestions

Connect London Datastore to Claude, Cursor, ChatGPT & more