KMB Bus MCP Server

Created By
kennyckka year ago
A MCP server which can query bus info, routes, eta, etc.
Overview

what is KMB Bus MCP Server?

KMB Bus MCP Server is a Model Context Protocol (MCP) server that provides real-time access to Hong Kong's KMB (九龍巴士) and Long Win Bus (龍運巴士) route information and arrival times, enabling Language Models to query bus service information.

how to use KMB Bus MCP Server?

To use the KMB Bus MCP Server, install the required dependencies, clone the repository, and configure your MCP client to connect to the server. You can then use various functions to query bus information.

key features of KMB Bus MCP Server?

  • Real-time bus arrival information (ETA)
  • Comprehensive bus route queries
  • Bus stop information and searches
  • Route-stop mapping
  • Caching system to optimize API calls
  • Bilingual support (English and Traditional Chinese)

use cases of KMB Bus MCP Server?

  1. Querying real-time bus arrival times for commuters.
  2. Finding bus routes and stops for trip planning.
  3. Integrating bus information into applications for enhanced user experience.

FAQ from KMB Bus MCP Server?

  • What data source does the server use?

The server utilizes the official KMB/LWB Open Data API for real-time data.

  • Is there a limit on API calls?

Yes, please be mindful of the API rate limits set by the KMB/LWB Open Data API.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kennyckk
Star
2
Language
Python
License
-

Recommend Servers

View All
Crevio

a day 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)

19 hours ago