Skip to main content
Glama
wassimbenaissa

Navitia MCP Server

by wassimbenaissa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Navitia MCP Server

No user-submitted related servers found.

    Related Servers

    • Bay Area Transit MCP

      srivastsh
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying real-time BART and SF Muni transit data, including departures, trip planning, fares, advisories, routes, alerts, vehicle positions, and schedules, from any MCP-compatible client.
      1
      MIT

    • mcp-hsl

      devusvulgaris
      A
      license
      A
      quality
      B
      maintenance
      An MCP server exposing Greater Helsinki public transport data from Digitransit, enabling LLM hosts to answer live transit queries, plan journeys, and fetch stop departures via natural language.
      3
      2 npm
      MIT

    • BVG MCP Server

      uniquename
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with the Berlin Public Transport (BVG) API to search for locations and plan journeys. It provides real-time access to departures, arrivals, trip details, and vehicle tracking within Berlin's transit network.
      MIT

    • Tutu MCP

      nyxandro
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching for buses and trains, and when direct routes are unavailable, it provides the underlying data needed to assemble multi-leg itineraries with transfers.
      4 npm
      ISC
    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.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: search_places handles geocoding, search_pt_objects resolves PT identifiers, and plan_journey covers routing. The schedule/departure tools overlap somewhat, but their descriptions differentiate granularity well enough for an agent to choose correctly.

    Naming Consistency3/5

    Naming is readable and grouped by domain (search_*, *_schedules, next_*), but it does not follow a single consistent verb_noun pattern. places_nearby and plan_journey deviate from the otherwise mostly noun-based tool names.

    Tool Count5/5

    The 9 tools are well-scoped for a public-transport MCP server. Each tool covers a distinct part of the workflow—place search, PT-object resolution, journey planning, and multiple schedule/departure queries—without unnecessary redundancy.

    Completeness5/5

    The set covers the full read-only workflow: resolve places and PT objects to IDs, plan journeys, and query departures, arrivals, or timetables at stop, line, and route granularity. There are no obvious dead ends because the search tools explicitly feed the routing and schedule tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources