Deutsche Bahn Mcp Server

Created By
PaulvonBerg9 months ago
A comprehensive Model Context Protocol (MCP) server that provides unified access to Deutsche Bahn (DB) and German mobility APIs. Built with Python, FastAPI, and FastMCP for seamless integration with Claude Desktop and other MCP clients.
Overview

What is Deutsche Bahn MCP Server?

The Deutsche Bahn MCP Server is a comprehensive Model Context Protocol (MCP) server that provides unified access to Deutsche Bahn (DB) and German mobility APIs, facilitating seamless integration with various MCP clients.

How to use Deutsche Bahn MCP Server?

To use the MCP server, deploy it locally or in the cloud, and connect to it by adding the URL to your MCP Client: https://db-mcp.datamonkey.tech/mcp.

Key features of Deutsche Bahn MCP Server?

  • Unified access to DB and German mobility APIs
  • Built with Python, FastAPI, and FastMCP for high performance
  • Open-source and community-driven development

Use cases of Deutsche Bahn MCP Server?

  1. Accessing real-time transport data from Deutsche Bahn.
  2. Integrating mobility services into applications.
  3. Providing users with up-to-date information on timetables and disruptions.

FAQ from Deutsche Bahn MCP Server?

  • Is the Deutsche Bahn MCP Server open-source?

Yes! The server is fully open-source, and contributions are welcome.

  • How can I deploy the MCP server?

You can deploy it locally or in the cloud using the provided server command.

  • What technologies are used in the MCP server?

The server is built using Python, FastAPI, and FastMCP.

Server Config

{
  "mcpServers": {
    "deutschebahn": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://db-mcp.datamonkey.tech/mcp",
        "--transport",
        "http-only"
      ]
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
PaulvonBerg
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 hours ago