Real timetable data for every AI assistant.

Connected in 30 seconds

One URL, no account, no key. Here is how in your client:

claude mcp add --transport http imtakt https://api.imtakt.dev/mcp

{
  "mcpServers": {
    "imtakt": {
      "url": "https://api.imtakt.dev/mcp"
    }
  }
}

code --add-mcp '{"name":"imtakt","type":"http","url":"https://api.imtakt.dev/mcp"}'

codex mcp add imtakt --url https://api.imtakt.dev/mcp

gemini mcp add --transport http imtakt https://api.imtakt.dev/mcp

{
  "mcpServers": {
    "imtakt": {
      "serverUrl": "https://api.imtakt.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "imtakt": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.imtakt.dev/mcp"
      ]
    }
  }
}

Five tools

The same five commands as the CLI and HTTP API. All read-only.

• imtakt_find

  Finds the stop for a place name and says how sure the match is.

  Ask for example: “Which station is Frankfurt?”

• imtakt_plan

  Compares journeys by time, duration, changes, Deutschlandticket and connection risk.

  Ask for example: “Munich to Berlin, arriving before noon, Deutschlandticket only.”

• imtakt_show

  Opens one journey with every leg, transfer time and walk.

  Ask for example: “How tight is the change in Fulda?”

• imtakt_status

  Reads the next departures at a stop with reported delays.

  Ask for example: “What leaves Köln Hbf in the next 20 minutes?”

• imtakt_follow

  Follows one train or bus and shows its next stops.

  Ask for example: “Where is my ICE right now?”

Also included: Prompts imtakt_trip and imtakt_commute for a trip and a commute · Resources imtakt://harness (the flow) and imtakt://meta (endpoints)

What a conversation looks like

Example. In a real conversation times and lines come live from the timetable.

Why ImTakt

Questions