Skip to main content
Glama
belgrano9

SNCF MCP Server

by belgrano9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SNCF MCP Server

No user-submitted related servers found.

    Related Servers

    • data-sncf

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying SNCF Open Data (train schedules, stations, punctuality, etc.) through natural language or direct tool calls, with dataset search, metadata retrieval, and ODSQL querying.
      6 npm
      MIT

    • TravelOS

      NicoLeblanc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching TGV Max train journeys across multiple departure stations with scheduling constraints, and resolving SNCF station names, directly through natural language.
      MIT

    • swisstrip-mcp

      Fabsbags
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to Swiss Federal Railways (SBB/CFF/FFS) data: train schedules, station search, ticket prices, and direct ticket purchase links.
      6
      46 npm
      -

    • SNCF API MCP Server

      Kryzo
      F
      license
      Not graded
      quality
      D
      maintenance
      A modular Python wrapper for the SNCF API that integrates with Claude Desktop, enabling intelligent journey planning and train information retrieval across France's railway network.
      18
      -
    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

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_trains finds journeys, find_station resolves station names, and get_train_prices retrieves pricing. Although search_trains and get_train_prices share origin/destination parameters, their descriptions and return types make them unambiguous.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern with lowercase and underscores: search_trains, find_station, get_train_prices. This is consistent and predictable.

    Tool Count5/5

    With 3 tools, the server is minimal but well-scoped for train journey searching. Each tool serves a necessary function and there is no redundancy.

    Completeness4/5

    The server covers the core workflow: station lookup, journey search, and price lookup. Missing booking or real-time status, but these are beyond the apparent scope. The experimental nature of get_train_prices introduces some uncertainty, but the surface is otherwise complete for planning.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources