Skip to main content
Glama

Related Servers

Alternatives to TrainRouter Atlas

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Locally-run MCP server that lets MCP clients search Japanese railway operators, lines, and stations, and retrieve station/line geometries as GeoJSON, operating kilometers, daily passenger trends, and nearest-station lookups from open linked data. It also computes simple network routes with transfer and stop counts, while explicitly excluding timetables, travel times, and through services.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for OpenStreetMap offering geocoding, routing, route optimization, isochrones, and POI search—requiring no API key and built for AI travel planning.
      11
      561 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that queries Russian Railways (ticket.rzd.ru) for train schedules, car types, prices, and seat availability. It provides official RZD links for manual booking but does not log in, book, or pay.
      59 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An (unofficial) MCP server for the Deutsche Bahn Timetables API — station search, planned departures, and real-time changes (delays, platform changes, cancellations) as tools for Claude and other MCP clients.
      4
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to structured Japanese railway data, enabling station searches without an API key and live Shinkansen timetable, fare, seat class, and stop queries with an Ekispert API key.
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes the Deutsche Bahn public transport API to any MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.). Five tools cover station search, departures, journey planning, trip details, and nearby stations.
      6
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a clearly distinct core purpose (text search, id lookup, curated famous list, country listing, sleeper listing, city-pair lookup, dataset stats). There is mild overlap between the curated lists (famous_routes, night_trains, routes_in_country) and search_routes with filters, but the descriptions explicitly tell the agent when to prefer each. An agent should reliably pick the right tool.

    Naming Consistency4/5

    All names use consistent snake_case and are immediately readable. The convention mixes verb-first (search_routes, get_route) with resource-first (famous_routes, night_trains, city_pair, atlas_stats), but the split is predictable enough that it does not impede selection.

    Tool Count5/5

    Seven tools is well-scoped for a read-only train-atlas server: one search, one detail fetch, three curated browsing views, one corridor lookup and one metadata snapshot. No tool feels redundant or missing at this granularity.

    Completeness4/5

    The surface covers the main discovery paths — free-text search, exact detail, famous routes, country browse, sleeper browse, city pairs and dataset stats — which is strong CRUD-equivalent coverage for a read-only atlas. Minor gaps remain (no standalone category-browse tool, no operator/rolling-stock filter, no related-route traversal), but agents can work around them via search_routes filters.

    Maintenance

    ActivityMaintained
    ResponsivenessUsually handled