Db Rail
DB Rail MCP — German + European rail and public transport, keyless.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http db-rail 'https://gateway.pipeworx.io/db-rail/mcp'{
"mcpServers": {
"db-rail": {
"type": "http",
"url": "https://gateway.pipeworx.io/db-rail/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-db-rail
DB Rail MCP — German + European rail and public transport, keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1855+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
dbrail_locations | Search German / European rail stations, stops, and places by name (e.g. "Berlin Hbf", "München", "Zürich HB"). Returns matches with a stop id, coordinates, and country. Keyless. You do NOT have to call this first — dbrail_departures, dbrail_arrivals and dbrail_journeys all accept a plain station name and resolve it themselves; use this when you want to disambiguate between similarly-named stations or need coordinates. |
dbrail_departures | Live departures board for a German / European station. Pass a station NAME ("Berlin Hbf") or a stop id from dbrail_locations. Returns upcoming departures with line/train number, destination, scheduled and real-time departure, delay in minutes, platform/track, and operator. Keyless, real-time where the operator publishes it. |
dbrail_arrivals | Live arrivals board for a German / European station. Pass a station NAME ("München Hbf") or a stop id from dbrail_locations. Returns upcoming arrivals with line/train number, origin, scheduled and real-time arrival, delay in minutes, platform/track, and operator. Keyless, real-time where the operator publishes it. |
dbrail_journeys | Plan a multi-leg rail / public-transport journey between two places in Europe. Pass station NAMES ("Berlin Hbf" -> "München Hbf") or stop ids. Returns route options, each with total duration, number of transfers, and every leg (mode, line, from/to with platforms, scheduled + real-time times). Keyless. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"db-rail": {
"url": "https://gateway.pipeworx.io/db-rail/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/db-rail/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1855+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/dbrail_locations \
-H 'Content-Type: application/json' \
-d '{"query":"Berlin Hbf"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/dbrail_locations. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"db-rail": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-db-rail"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-db-railIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Db Rail data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Db Rail?
DB Rail MCP — German + European rail and public transport, keyless.
How do I install Db Rail?
It runs as a remote server. In Claude Code: claude mcp add --transport http db-rail 'https://gateway.pipeworx.io/db-rail/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Db Rail need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Db Rail open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Db Rail?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.