korea-transit-mcp
Related Servers
Alternatives to korea-transit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides MCP tools to query real-time bus arrivals, bus locations, road traffic, and parking availability in Daegu, South Korea.61MIT
- AlicenseAqualityCmaintenanceEnables LLMs to query realtime bus and metro data across Chinese cities without any login or API key, covering keyword search, nearby stops, stop and line details, live vehicle positions and ETAs, and bus-plus-metro transfer planning. Departure predictions at a line's first stop cover the full service day, including last departures and the next bus after a specified time.152MIT
- AlicenseNot gradedqualityBmaintenanceEnables realtime bus arrival queries, route and stop searches, nearby station lookups, and transit planning for Chelaile-supported cities through MCP tools.11MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude and Cursor to query Korean public APIs for weather, air quality, holidays, tourism, Bank of Korea exchange and interest-rate statistics, and Seoul real-time subway arrivals using user-supplied API keys.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI to query real-time Korean public data including weather, real estate prices, air quality, economic indicators, and business registration via natural language.1MIT
- AlicenseBqualityDmaintenanceEnables natural language queries to KORAIL public data including station facilities, train operations, statistics, freight, and urban rail information across various AI clients.983MIT
TDQS
Scored across 12 tools
Most tools have sharply distinct roles, and the descriptions explicitly sequence dependent tools (list_cities → search_bus_stops → get_bus_arrivals, and find_direct_routes → find_transfer_routes as a fallback). The only real overlap is search_routes vs get_route_info, which both return origin/destination and first/last times, and search_bus_stops vs find_nearby_stops, though those differ by name vs coordinates.
Every tool follows a consistent snake_case verb_noun pattern (list_cities, get_bus_locations, find_direct_routes, search_bus_stops, analyze_headway). Verb choice is also semantically meaningful: list/search for discovery, get for direct lookup, find for route computation.
12 tools is well within the ideal 3-15 range, and each one earns its place by covering a distinct step in a bus-trip workflow (city → stop → route → arrival → routing → headway). No obvious filler or near-duplicate tools.
The bus domain is covered end to end: discovery by name and by coordinates, route lookup, stop sequences, real-time arrivals and vehicle positions, single-transfer routing, and headway analysis. Minor gaps remain, such as no fare/service-alert information and no subway or intercity coverage despite the 'korea-transit' server name (Seoul is also explicitly unsupported).