sitp-bogota-mcp
Related Servers
Alternatives to sitp-bogota-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables searching for TransMilenio and SITP bus routes in Bogotá with live GPS tracking, nearby stops, and estimated arrivals.810-
- AlicenseAqualityBmaintenanceConnects Claude to live TransMilenio bus positions, official schedules, stop arrivals, alerts, and route history so users can ask natural-language questions about Bogotá transit and compare scheduled service with what is actually on the street.131MIT
- AlicenseAqualityCmaintenanceEnables querying Budapest and Hungarian public transport via the official BKK FUTÁR API, including stop lookup, departure boards, trip planning, direct MÁV train connections, and service alerts.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying global transit data including agencies, routes, stops, and departures through a GTFS aggregator.64 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables real-time Singapore bus arrival lookups, bus stop search, and nearby stop discovery through plain-language queries.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying LA Metro bus and rail route rosters, stop locations, and live service cancellations from Metro's open API.79 npmMIT
TDQS
Scored across 7 tools
Each tool targets a distinct query type: stop search by name/code, stops by coordinates, routes at a stop, route details, upcoming buses, GTFS metadata, and trip planning. The only mild overlap is between buscar_paraderos and paraderos_cercanos (both return stop lists), but the input difference (text vs coordinates) is clearly documented. rutas_en_paradero vs info_ruta is the inverse relationship (stop→routes vs route→details) and is legible from the names.
All names are Spanish snake_case, which is consistent, but the grammatical patterns are mixed: verb-first (buscar_paraderos, planear_viaje), noun-adjective (paraderos_cercanos, proximos_buses), and noun_noun (info_ruta, info_datos). The result is readable and domain-idiomatic but lacks a predictable verb_noun template across the set.
Seven tools is well-scoped for a transit data server, with each tool mapping to a distinct user intent (search, proximity, route lookup, departures, planning, metadata). No tool feels redundant or out of place, and none of the core capabilities are missing.
The surface covers the full read-only transit lifecycle: discovery (search/nearby), route detail, departures/realtime, and end-to-end trip planning, plus metadata about data freshness. Minor gaps exist (e.g. no route geometry/shape or a way to list/browse all routes without knowing a code), but agents can work around these.