Transport NSW MCP Server

If you already use Transport NSW, the transport nsw mcp server is the piece that lets your assistant work with it directly. Facilitates interaction with the Transport NSW API using the Model Context Protocol for accessing real-time transport data.

What the server does

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

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

• 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

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: OPEN_TRANSPORT_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by danhussey; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Transport NSW's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.