OpenBusData

io.github.AndrewAuburyPublished by GitHub account AndrewAuburyv1.0.2Updated Oct 24, 2026

MCP server for UK Bus Open Data with timetable parsing, journey planning and live tracking.

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server for the UK Bus Open Data Service, letting an assistant search stops, find routes, plan journeys and track live buses.

What you can do
  • Search UK bus stops by fuzzy text
  • Find routes serving a pair of stops
  • Plan journeys, including direct and chained multi-leg trips, to arrive by a given time
  • Query timetables, fares, disruptions and cancellations
  • Show real-time bus locations
When to use it
Useful when you want an assistant to answer UK public transport questions: which stops exist near a place, which routes connect two stops, how to get somewhere by a certain time, or where a bus currently is.
Requirements
Runs locally as a Python package (uvx openbusdata-mcp or pip install openbusdata-mcp). Requires a Bus Open Data Service API key supplied in the OPENBUS_API_KEY environment variable; a free key is available from the service. Network access to the Bus Open Data Service is needed.
Before you install
The server needs your OPENBUS_API_KEY, which is sent to the Bus Open Data Service; keep it out of shared configuration files. Queries and searched locations go to that third-party service. The tools are read-only lookups, but timetable and live data reflect the upstream service and may be incomplete or delayed.

Installation

In SourceWeft

  1. Open OpenBusData in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

OpenBusData MCP Server

mcp-name: io.github.AndrewAubury/openbusdata

MCP server for the UK Bus Open Data Service with rich timetable parsing, stop search, route discovery, journey planning and real-time bus tracking.

Features

  • Live API tools — query timetables, fares, disruptions, cancellations and real-time bus locations
  • Stop search — fuzzy text search across every bus stop in the UK
  • Route finder — discover all routes serving a pair of stops
  • Journey planner — "get to X by Y o'clock" with support for direct and chained multi-leg journeys
  • Live tracking — see exactly where buses are right now

Installation

Option 1: via uvx (recommended — no install needed)

bash
uvx openbusdata-mcp

Option 2: via pip

bash
pip install openbusdata-mcp

Configuration

Set your Bus Open Data Service API key as an environment variable:

bash
export OPENBUS_API_KEY="your-api-key-here"

Get a free key at data.bus-data.dft.gov.uk.

Usage

With uvx (recommended)

Add to your MCP client (Claude Desktop, Cursor, etc.):

json
{  "mcpServers": {    "openbusdata": {      "command": "uvx",      "args": ["openbusdata-mcp"],      "env": {        "OPENBUS_API_KEY": "your-api-key-here"      }    }  }}

With pip install

json
{  "mcpServers": {    "openbusdata": {      "command": "openbusdata-mcp",      "env": {        "OPENBUS_API_KEY": "your-api-key-here"      }    }  }}

Development

bash
# Create virtual environmentpython -m venv .venvsource .venv/bin/activate  # or .venv\Scripts\activate on Windows
# Install dependenciespip install -e ".[dev]"
# Run serverpython -m openbusdata_mcp.server

License

MIT

Source: README.md at commit 35a3296

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.