Skip to main content
Glama
jorekai

DB Timetable MCP Server

by jorekai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to DB Timetable MCP Server

No user-submitted related servers found.

    Related Servers

    • DB Timetable MCP Server

      zzuisa
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Deutsche Bahn's timetable data through MCP, enabling real-time train schedules, station search, and change tracking for German railway stations.
      4
      80 npm
      MIT

    • db-fahrplan

      capraCoder
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to access live Deutsche Bahn timetable data, including connections, departure and arrival boards, platforms, delays, fares, and disruptions, by querying bahn.de directly with no API key.
      9
      MIT

    • db-fahrplan-mcp

      eric134422
      A
      license
      A
      quality
      B
      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

    • IndianRailwaysMCP

      Shadhai
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query real-time Indian Railways data including train schedules, live status, PNR status, seat availability, fares, and coach positions via the Model Context Protocol.
      -

    • db-mcp

      Amor216
      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
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: findStations searches for stations, getCurrentTimetable retrieves real-time data, getPlannedTimetable fetches future schedules, and getRecentChanges tracks recent changes. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern with three tools starting with 'get' and one with 'find', all using camelCase. The minor deviation is 'findStations' versus 'getX', but it remains readable and predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of accessing railway timetable data. Each tool serves a specific and necessary function, providing a focused set without being too sparse or overwhelming.

    Completeness4/5

    The tool set covers core operations for timetable data: searching stations, retrieving current and planned schedules, and tracking changes. A minor gap is the lack of tools for modifying or managing data (e.g., CRUD operations), but this may be intentional for a read-only server, and agents can work around this limitation.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources