Data & Analytics · SNCF + Claude
SNCF MCP with Claude: Faster Rail Journey Planning and Live Service Checks
The short answer
Claude works with SNCF through the Model Context Protocol, a secure connector that lets Claude request train journeys, station details, schedules and service status from SNCF's data. Staff ask questions in plain language, and Claude returns the answer. Access uses an API key, and the organisation controls what Claude can read.
What is SNCF?
SNCF is France's national railway service for passenger train journeys. It runs stations, timetables and live travel information across the country. Developers use its data to build route planners and travel tools. Businesses use it for travel planning, logistics coordination and staff mobility. Operations and travel teams rely on accurate, current rail information to plan trips and keep people moving.
How Claude connects to SNCF through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and a tool. Once SNCF is connected this way, Claude can use SNCF's data to answer questions it would otherwise not be able to answer reliably.
Once connected, Claude can typically search for train journeys between two places, look up station names and details, check timetables for a given date, and monitor whether services are running normally. You ask in everyday language, and Claude turns that into the right requests and explains the results clearly.
Permissions and approvals keep people in charge. The connection uses an API key, and the organisation decides which parts of the data Claude may access. Read-only lookups can run freely, while any action that affects bookings or internal records can be set to require a person's approval before it goes ahead.
What you can automate
Travel desk journey planning
Travel coordinators ask Claude to find suitable train options between cities for a group of staff. Claude searches journeys and timetables, compares departure times and connections, and presents a short shortlist. The coordinator reviews the options and makes the final choice, which saves time compared with searching manually across several screens.
Station lookup for field teams
Field service and sales teams often need to know which station serves a client site or how to reach it. Claude can look up station names, locations and details, then summarise the best arrival point. This helps teams prepare briefings and avoid wasted time at the wrong platform or stop.
Service disruption checks
Operations managers can ask Claude whether services on a given route are running normally before a important meeting or delivery. Claude checks current service information and reports any reported disruption. Managers can then decide whether to reschedule, reroute or notify affected people early.
Logistics and delivery planning
Logistics teams that move samples, documents or equipment by rail can use Claude to check timetables and typical transit options between depots and client sites. The team gets a clear plan showing journey options and timings, which supports more reliable scheduling of time-sensitive shipments.
Commuter and mobility support for HR
HR and facilities teams supporting staff who commute by rail can use Claude to answer common questions about routes, station access and typical journey times. This creates a consistent source of information for employees and reduces repeated queries to the team.
An end-to-end workflow: Event travel coordination for a visiting client team
TriggerA client team of twelve is booked to visit the Paris office, and the event coordinator logs the request in the ticketing system.
Claude reads the ticket in the ticketing system and extracts the origin city, travel date and preferred arrival time.
Claude searches SNCF journeys and timetables for suitable train options and identifies the most practical arrival station.
Claude checks service status for the chosen routes to flag any reported disruption on the travel date.
Claude drafts a travel summary with journey options, station details and timings, and adds it to the ticket.
The coordinator reviews the summary in Microsoft 365, confirms the options with the client, and approves the final plan.
The confirmed itinerary is saved to the shared calendar so every attendee receives the same travel details.
OutcomeThe coordinator spends far less time on manual timetable searches, and the client team receives a clear, checked travel plan with fewer last-minute surprises. Results vary by organisation and workflow.
How we set it up
Free automation audit
We review how your teams currently plan rail travel, check stations and monitor services. We identify the workflows where Claude and SNCF data would save the most time, at no cost.
Secure API key connection
We connect Claude to SNCF using an API key, stored securely and limited to the access your workflows need. Where a dedicated MCP server is available, we use it; otherwise we use a secure managed connector.
Workflow design
We design the end-to-end process across SNCF and your other systems, such as Microsoft 365, CRM, ERP or ticketing. We agree which actions run automatically and which require a person's approval.
Testing with real cases
We test the workflow against real past journeys and requests from your team. We check accuracy, refine the prompts and confirm the results match what your staff expect.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team to use the workflow confidently. We review performance with you after launch and adjust where needed.
Who benefits
- Travel and events coordinators
- Faster journey searches and clearer itineraries, with fewer manual timetable checks.
- Operations managers
- Quicker visibility of service status, helping them respond early to disruption.
- Logistics and field service leads
- Better planning of rail-based deliveries and visits to client sites.
- HR and facilities teams
- A consistent source of commuting and station information for employees.
Security and control
- Access uses an API key with least-privilege permissions, limited to the data each workflow needs.
- Read-only lookups are separated from any action that affects bookings or internal records.
- People approve consequential actions before they are carried out.
- Audit logs record what Claude accessed and what it did, supporting review and accountability.
- Live travel information can change, so staff should confirm critical journeys before committing.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can use this workflow with data protection requirements built into the design. Indian organisations are supported under the Digital Personal Data Protection Act, 2023, and organisations in the UAE and Saudi Arabia follow their local data protection laws. We choose the hosting region for your Claude deployment to meet your legal and contractual requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the SNCF MCP server do?
The SNCF MCP server lets Claude securely access SNCF's rail data. Through it, Claude can typically search train journeys, look up stations, check timetables and monitor service status. The exact capabilities depend on the data SNCF makes available, and we confirm these during the free audit before building anything.
Is connecting SNCF to Claude secure?
The connection uses an API key and is set up with least-privilege access, so Claude only reaches the data a workflow needs. Actions that affect records can require human approval, and audit logs track activity. Security depends on how the connection is configured and maintained, so we design it with your IT team.
What can Claude do with SNCF once it is connected?
Once connected, Claude can answer questions such as which trains run between two cities on a date, where a station is, and whether a route has a reported disruption. It explains results in plain language and can pass information into your other systems, such as a ticket or shared calendar, with approval where needed.
How long does setup take?
Setup time depends on how many workflows you want and how many systems they touch. A focused single workflow is often quicker to launch than a set of linked processes. We give you a timeline after the free automation audit, once we understand your requirements and the access you need.
What plan or permissions do we need?
You need an SNCF API key with access suitable for your use. Access levels and availability are set by SNCF, so we check what your key permits during the audit. We then agree the permissions Claude needs and keep them as narrow as the workflow allows.