db-fahrplan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_API_KEY | Yes | Your DB API key | |
| DB_CLIENT_ID | Yes | Your DB API Client ID |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_stationA | Search German train stations and get their EVA numbers. Args: pattern: Station name, EVA number, or DS100 code. Prefix search - exact DB naming works best (e.g. "Stolberg(Rheinl)Hbf" rather than "Stolberg Hbf"). Umlauts often fail; try "*" as wildcard. |
| get_departuresA | Get the timetable for a station within one hour slice, including real-time data: delays (delay_minutes), platform changes, cancellations, and added trips such as replacement buses. Defaults to the current date and hour. Args: eva_no: EVA number of the station (e.g. "8000001" for Aachen Hbf). Use find_station to look it up. date: Day in YYMMDD format (e.g. "260713"). Defaults to today. hour: Hour in HH format, 00-23. Defaults to the current hour. |
| get_live_changesA | Get all known real-time changes for a station: delays, platform changes, cancellations. Covers the current operating day. Args: eva_no: EVA number of the station (e.g. "8000001" for Aachen Hbf). limit: Maximum number of stops to return (sorted by time). |
| get_recent_changesA | Get only the changes of the last 2 minutes for a station. Much smaller than get_live_changes - use for frequent polling. Args: eva_no: EVA number of the station (e.g. "8000001" for Aachen Hbf). limit: Maximum number of stops to return (sorted by time). |
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/eric134422/db-fahrplan-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server