How to connect SNCF to OpenClaw
Connect SNCF to OpenClaw with ClawLink: paste your SNCF key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
SNCFAPI KEYMCPAccess SNCF passenger-information data for train journeys, stations, schedules, service status, and transport-network discovery.. Once connected, OpenClaw can read and act on SNCF from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to SNCF access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical SNCF setup: install one ClawHub skill, connect SNCF in the browser, and OpenClaw can call real SNCF actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to SNCF.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect SNCF
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with SNCF?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect SNCF in the ClawLink dashboard — paste your SNCF API key once.
Verify the connection by asking OpenClaw:
Use SNCF to find nearby places and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once SNCF is connected in the dashboard, that agent calls the same 9 SNCF tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
SNCF MCP for OpenClaw
Looking for a SNCF MCP server for OpenClaw? ClawLink connects SNCF to OpenClaw and exposes 9 SNCF tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes SNCF integration works the same way.
What the OpenClaw SNCF integration can do
9 SNCF tools are ready for OpenClaw once the account is connected.
All 9 SNCF tools for OpenClaw
| Tool | What it does |
|---|---|
Find nearby places sncf_find_nearby_places | Find SNCF stations, stops, or points of interest near a geographic coordinate |
Get service status sncf_get_service_status | Get SNCF network service disruptions and affected lines, stations, or vehicle journeys for a |
Get station board sncf_get_station_board | Get upcoming departures or arrivals for an SNCF station, including scheduled and realtime times |
Get transport object sncf_get_transport_object | Get details for one SNCF network, line, route, station, stop, mode, company, or vehicle journey |
List coverage sncf_list_coverage | Get the SNCF transport-data coverage region and its current production horizon |
List transport objects sncf_list_transport_objects | Browse one supported SNCF transport-object collection, such as lines, networks, routes |
Plan journey sncf_plan_journey | Plan SNCF train journeys between two station/place IDs or coordinates for a requested departure |
Search places sncf_search_places | Find SNCF stations, addresses, administrative areas, or points of interest by name and return |
Search transport objects sncf_search_transport_objects | Search SNCF networks, modes, lines, routes, stations, or stop points by name and return |
Try it: find the SNCF tool you need
Browse the 9 SNCF tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use SNCF to find nearby places and walk me through the result in plain English.
Pull the relevant data from SNCF, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from SNCF, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from SNCF, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SNCF working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the SNCF API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected SNCF account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for SNCF. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right SNCF actions to the runtime in a format your agent can reliably use. | 9 tools for SNCF are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes SNCF to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect SNCF in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the SNCF key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the SNCF skill but can't call the tools
The ClawHub skill teaches OpenClaw about SNCF, but the calls run through the ClawLink plugin and your connected account. Make sure SNCF is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect SNCF from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling SNCF tools
SNCF tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every SNCF call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
SNCF returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for SNCF has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw SNCF integration?
Yes. ClawLink is the fastest way to connect OpenClaw to SNCF: link your SNCF account once in the browser and OpenClaw can call the SNCF API through 9 ready-made tools — no custom code or token handling.
How do I add SNCF to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink SNCF skill from ClawHub, then you click Connect in the dashboard to authorize SNCF. OpenClaw calls the tools from the next message — no config files, and the SNCF key you paste is stored server-side instead of in your environment.
How long does it take to connect SNCF to OpenClaw?
About two minutes. Sign in, click Connect next to SNCF in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring SNCF up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SNCF working from chat.
OpenClaw installed the SNCF skill but can't call the tools
The ClawHub skill teaches OpenClaw about SNCF, but the calls run through the ClawLink plugin and your connected account. Make sure SNCF is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture tools
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.