Skip to main content
Glama
Transport NSW API Client MCP

Transport NSW API Client MCP

by danhussey

Transport NSW API Client (MCP Implementation)

Tests

A Claude MCP for interacting with the Transport NSW API using direct HTTP requests.

About

This project implements a Model Context Protocol (MCP) service for Transport NSW's API.

Related MCP server: transport12 MCP Server

Setup

  1. Clone this repository

  2. Install dependencies using uv (fast Python package manager):

    uv venv
    uv sync
  3. Create a .env file with your API key:

    OPEN_TRANSPORT_API_KEY=your_api_key_here
  4. (Optional) Run the MCP Inspector:

    uv run mcp dev api.py

    And visit the server at http://localhost:5173 (port might be different).

Features

  • Stop Finder API: Find transport stops by name or coordinates

  • Alerts API: Get information about transport alerts and disruptions

  • Departure Monitor API: Get real-time departure information for transport stops

  • MCP Implementation: Structured as a Model Context Protocol service

Usage Examples

MCP Examples coming soon. Standard Python examples below:

Find Transport Stops

from api import find_transport_stops

# Search by name
stops = find_transport_stops(stop_name="Central Station")

# Search by coordinates (Central Station area)
central_station = '151.206290:-33.884080:EPSG:4326'
stops = find_transport_stops(coord=central_station, radius=500)

Get Transport Alerts

from api import get_transport_alerts

# Get all current alerts
alerts = get_transport_alerts()

# Get alerts for a specific date
date_alerts = get_transport_alerts(date='22-03-2025')

# Get train alerts only (mot_type=1)
train_alerts = get_transport_alerts(mot_type=1)

Monitor Real-time Departures

from api import get_departure_monitor

# Get departures from Central Station
departures = get_departure_monitor("200060")  # Central Station ID

# Get departures for a specific time
from datetime import datetime
time_departures = get_departure_monitor("200060", time="15:30")

# Get only train departures
train_departures = get_departure_monitor("200060", mot_type=1)  # 1 = Train

Demo Script

The project includes a comprehensive demo script that showcases all API functionality:

# Run the full demo
python demo.py

# Run specific sections
python demo.py --stops       # Stop finder demo
python demo.py --alerts      # Transport alerts demo
python demo.py --departures  # Departure monitoring demo

Testing

Local Testing

Run the complete test suite with pytest:

uv run pytest

Run with coverage reporting:

uv run pytest --cov=api

Continuous Integration

Tests automatically run on GitHub Actions for every push and pull request to the main branch. The workflow:

  1. Sets up Python 3.10

  2. Installs uv and project dependencies

  3. Runs tests with coverage reporting

To use this feature:

  1. Add your OPEN_TRANSPORT_API_KEY as a GitHub repository secret

  2. Push your code to GitHub

MCP Integration

This project follows the Model Context Protocol specification, allowing AI models to access Transport NSW data through a standardized interface.

Package Management

This project uses uv, a modern Python package manager written in Rust. Dependencies are managed through:

  • pyproject.toml: Defines project dependencies

License

This project is licensed under the MIT License.

Available Tools

3 tools
find_transport_stopsB
Find transport stops around a specific location.

Args:
    location_coord (str): Coordinates in format 'LONGITUDE:LATITUDE:EPSG:4326'
    stop_type (str): Type of stops to find: 'BUS_POINT', 'POI_POINT', or 'GIS_POINT'
    radius (int): Search radius in meters
    
Returns:
    API response with transport stops

Inputs: location_coord (required), stop_type, radius.

get_departure_monitorA
Get real-time departure monitor information for a specific stop from the Trip Planner API.
This function uses direct HTTP requests to the Transport NSW API.

Args:
    stop_id (str): Stop ID or global stop ID
    date (str, optional): Date in DD-MM-YYYY format. Defaults to today's date.
    time (str, optional): Time in HH:MM format. Defaults to current time.
    mot_type (int, optional): Mode of transport type filter. Options:
        1: Train
        2: Metro
        4: Light Rail
        5: Bus
        7: Coach
        9: Ferry
        11: School Bus
    max_results (int, optional): Maximum number of results to return. Default is 1.
    
Returns:
    list: Simplified list of departure information

Inputs: stop_id (required), date, time, mot_type, +1 more.

get_transport_alertsB
Get transport alerts from the Transport NSW API.

Args:
    date (str, optional): Date in DD-MM-YYYY format. Defaults to today's date.
    mot_type (int, optional): Mode of transport type filter. Options:
        1: Train
        2: Metro
        4: Light Rail
        5: Bus
        7: Coach
        9: Ferry
        11: School Bus
    stop_id (str, optional): Stop ID or global stop ID to filter by.
    line_number (str, optional): Line number to filter by (e.g., '020T1').
    operator_id (str, optional): Operator ID to filter by.

Returns:
    dict: API response containing alerts information

Inputs: date, mot_type, stop_id, line_number, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: find_transport_stops locates stops, get_departure_monitor provides real-time departures, and get_transport_alerts retrieves service alerts. There is no overlap in functionality, and the descriptions clearly differentiate their roles.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: find_transport_stops, get_departure_monitor, and get_transport_alerts. The naming is predictable and readable throughout the set.

    Tool Count3/5

    With only 3 tools, the set feels thin for a transport API client, lacking operations like route planning, trip details, or fare information. While the tools cover basic needs, the scope suggests more comprehensive coverage would be expected.

    Completeness3/5

    The tools provide core functionality for stops, departures, and alerts, but there are notable gaps. Missing operations include trip planning, route searches, service status beyond alerts, and fare queries, which are typical for a transport API and could limit agent effectiveness.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with the Berlin Public Transport (BVG) API to search for locations and plan journeys. It provides real-time access to departures, arrivals, trip details, and vehicle tracking within Berlin's transit network.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying real-time BART and SF Muni transit data, including departures, trip planning, fares, advisories, routes, alerts, vehicle positions, and schedules, from any MCP-compatible client.
      1
      MIT