tokyo-transit-mcp
Related Servers
Alternatives to tokyo-transit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables route planning and transit information retrieval for Japan using the public Transit API. Supports searching stations, planning routes, and checking departures.101MIT
- FlicenseAqualityDmaintenanceProvides access to Tokyo's WBGT (Wet Bulb Globe Temperature) heat index forecast and real-time data from multiple observation points using Japan's Ministry of the Environment official data for heat stroke prevention.3-
- AlicenseAqualityCmaintenanceEnables AI assistants to answer questions about Japan's railway network with accurate track-connection data, including station neighbors and local subgraphs for all 9,043 stations nationwide.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Japanese public transit journey planning with interactive map UI, enabling station search, route planning, and departure lookups via natural language.MIT
- AlicenseBqualityFmaintenanceEnables AI clients to access Boston's MBTA public transit data, including real-time predictions, schedules, route planning, and service alerts.321Apache 2.0
- AlicenseAqualityBmaintenanceJapan Operations OS for AI agents — 14 knowledge domains covering regulations, protocols, calendar, travel, food culture, language, disaster safety, daily life, and persistent memory. 31 MCP tools via REST + Streamable HTTP.31MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes, such as route search, fare search, timetable lookup, and station info. Slight overlap exists between search_route and get_weather since both provide weather-related AI advice, but they serve different primary intents. The ferry listing vs. route search tools are also clearly separated.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like search, get, and list. This creates a predictable and uniform naming convention across the entire set.
With 10 tools, the server is well-scoped for a comprehensive Tokyo transit system, covering route planning, fares, timetables, ferries, buses, operators, and weather. Each tool serves a distinct functional area without unnecessary redundancy.
The tool set covers core transit needs well: route search, fares, timetables, station info, operators, ferries, and buses. Minor gaps include lack of real-time disruption alerts as a dedicated tool, though search_route partially detects suspensions. Missing line-specific station lists are handled via get_operator_routes.