A Model Context Protocol (MCP) server for TfNSW's realtime alerts API
Connect TfNSW Realtime Alerts to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for TfNSW's realtime alerts API. The tfnsw realtime alerts mcp server is what makes that connection.
A Model Context Protocol server for Transport for NSW's (TfNSW) Realtime Alerts API. This server provides tools to access and interact with real-time transport alerts and information via Large Language Models.
This TypeScript-based MCP server implements integration with Transport for NSW's Realtime Alerts system. It enables AI assistants to access up-to-date information about transport disruptions, planned works, and other important alerts across the NSW transport network.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
get-transport-alerts — Retrieve current transport alertsResources — The Resources tool exposed by this serverTools — The Tools tool exposed by this serverPrompts — The Prompts tool exposed by this serverDebugging — You can use the MCP Inspector for debugging, which is available as a package script:Configuration is passed through the environment: NSW_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.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. TfNSW Realtime Alerts's toolset — get-transport-alerts, Resources, Tools and 2 more — is a fair guide to whether it matches your workflow. It is maintained by piddlingtuna; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get-transport-alerts | Retrieve current transport alerts |
| Resources | The Resources tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
| Prompts | The Prompts tool exposed by this server. |
| Debugging | You can use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) for debugging, which is available as a package script: |
{
"mcpServers": {
"tfnsw-realtime-alerts": {
"command": "npx",
"args": [
"-y",
"tfnsw-realtime-alerts-mcp-server"
],
"env": {
"NSW_TRANSPORT_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NSW_TRANSPORT_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.