Singapore LTA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LTA_API_KEY | Yes | Your LTA DataMall API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bus_arrivalA | Get real-time bus arrival information for a specific bus stop and optionally a specific service number. Returns estimated arrival times, bus locations, and crowding levels. |
| station_crowdingA | Get real-time MRT/LRT station crowdedness level for a particular train network line. Updates every 10 minutes. |
| train_alertsA | Get real-time train service alerts including service disruptions and shuttle services. Updates when there are changes. |
| carpark_availabilityA | Get real-time availability of parking lots for HDB, LTA, and URA carparks. Updates every minute. |
| travel_timesA | Get estimated travel times on expressway segments. Updates every 5 minutes. |
| traffic_incidentsA | Get current road incidents including accidents, roadworks, and heavy traffic. Updates every 2 minutes. |
| station_crowd_forecastC | Get forecasted MRT/LRT station crowdedness levels in 30-minute intervals. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct domain (bus arrivals, carpark availability, MRT crowding, traffic incidents, train alerts, travel times) with no functional overlap, making it easy for an agent to select the right tool.
All tool names follow a consistent snake_case pattern with descriptive noun combinations (e.g., bus_arrival, carpark_availability), ensuring predictability and clarity.
With 7 tools, the server covers key real-time transport data domains (bus, carpark, MRT, traffic, train, expressway) without being too sparse or overwhelming.
The tool set provides broad coverage of real-time transport data, though it lacks tools for route planning or fare information, which are secondary to the real-time focus.