SNCF MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNCF_API | Yes | Your SNCF API key from the SNCF Digital API Portal |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_trainsA | Search for train journeys between two stations with pagination. Args: origin: Starting station name (e.g., "Paris Est", "Lyon") destination: Destination station name (e.g., "München Hbf", "Barcelona") departure_datetime: Optional datetime. Accepts flexible formats: - ISO: "2025-11-28 08:00" (RECOMMENDED) - European: "28/11/2025 08:00" - Written: "November 28, 2025 8:00am" If not provided, searches from current time. page: Page number for pagination (default: 1). Shows 10 results per page. Request different pages to see more trains (e.g., page=2, page=3). |
| find_stationA | Search for a train station by name and return matching options. Useful for checking station names before searching for journeys, or when you're not sure of the exact station name. Args: station_name: Station name to search for (e.g., "Paris", "Munich", "Lyon") Returns: A formatted string showing matching stations with their IDs and full names. |
| get_train_pricesA | Get train prices (EXPERIMENTAL - Educational Proof of Concept). ⚠️ WARNING: This is an experimental feature that attempts to scrape prices from SNCF. It may not work due to:
For production use, consider:
Args: origin: Origin station name (e.g., "Paris", "Lyon") destination: Destination station name (e.g., "Marseille") departure_datetime: Date/time in flexible formats (default: today) page: Page number for pagination (default: 1) per_page: Results per page (default: 5, max: 20) Returns: Formatted string with price information (if available) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/belgrano9/sncf_mcp_server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server