Singapore LTA MCP Server

Created By
arjunkmrma year ago
MCP server to access Singapore's LTA data
Overview

what is Singapore LTA MCP Server?

The Singapore LTA MCP Server is an API server that provides real-time access to transportation information from Singapore's Land Transport Authority (LTA), including bus arrivals, traffic conditions, and train service updates.

how to use Singapore LTA MCP Server?

To use the server, install it via Smithery using the command: npx -y @smithery/cli install @arjunkmrm/mcp-sg-lta --client claude. You will also need to register for an API key from the LTA DataMall.

key features of Singapore LTA MCP Server?

  • Real-time bus arrival information
  • Updates on MRT/LRT station crowding levels
  • Alerts for train service disruptions
  • Availability of parking lots in real-time
  • Estimated travel times on expressway segments
  • Current road incidents updates

use cases of Singapore LTA MCP Server?

  1. Commuters checking bus arrival times before heading to the bus stop.
  2. Travelers monitoring crowd levels at MRT stations to avoid peak hours.
  3. Drivers looking for real-time traffic updates to plan their routes.
  4. Users checking carpark availability before arriving at their destination.

FAQ from Singapore LTA MCP Server?

  • How do I get an API key?

Register for an account on LTA DataMall, subscribe to the API services, and obtain your API key from the dashboard.

  • Is the server free to use?

Yes, the server is free to use, but you need to register for an API key.

  • How often is the data updated?

The data is updated at various intervals, with bus arrival times and traffic incidents updated every few minutes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
arjunkmrm
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

12 hours ago
Crevio

a day ago