RailRoute journey planner

Working · 2.1 s

in.railroute/journey-plannerv1.3.0 Domain verified

Plan intercity journeys in India by train, flight or both, with a fare for every travel class.

Maps & Travel

Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://www.railroute.in/api/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

check_train_options Read-only

Live seat availability per class for one train on one date, plus every other way to book it when the through ticket will not confirm: a split at an intermediate station, boarding earlier, alighting later. This is the tool that rescues a waitlisted train. It spends a metered upstream call, so ask it about trains the traveller is actually considering rather than sweeping a list.

tostring, required

Station code the traveller alights at

datestring, required

fromstring, required

Station code the traveller boards at

train_numberstring, required

quotastring

include_racboolean

RAC is a ticket that carries a right to board, so it counts as bookable by default.

Tools (8)

check_train_options

read-only

Argument	Type	Description
to*	string	Station code the traveller alights at
date*	string
from*	string	Station code the traveller boards at
quota	string
include_rac	boolean	RAC is a ticket that carries a right to board, so it counts as bookable by default.
train_number*	string

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "train_number",
    "from",
    "to",
    "date"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Station code the traveller alights at"
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "from": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Station code the traveller boards at"
    },
    "quota": {
      "enum": [
        "GN",
        "TQ",
        "PT",
        "LD",
        "SS"
      ],
      "type": "string",
      "default": "GN"
    },
    "include_rac": {
      "type": "boolean",
      "default": true,
      "description": "RAC is a ticket that carries a right to board, so it counts as bookable by default."
    },
    "train_number": {
      "type": "string",
      "pattern": "^\\d{4,6}$"
    }
  }
}

find_place

Turn what somebody typed into RailRoute place ids. ALWAYS call this before plan_journey. A place is a city with all of its stations and airports — Mumbai covers CSMT, LTT, Dadar, Bandra Terminus and the airport — so the planner can choose the right terminal rather than making the traveller do it. Typing a station code ("CSMT") finds the city and says which terminal matched.

read-only

Argument	Type	Description
limit	integer
query*	string	A city, station name or station code

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A city, station name or station code"
    }
  }
}

journey_calendar

Day-by-day service over a span of dates for a station pair: which days have a direct train and which have none, plus the weekly pattern. Use this when somebody is flexible about when they travel, or asks 'does it run on Sundays'. Timetable only — it says nothing about seats.

read-only

Argument	Type	Description
to*	string	Destination station code
days	integer
from*	string	Origin station code
start_date*	string	First day of the span

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "from",
    "to",
    "start_date"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Destination station code"
    },
    "days": {
      "type": "integer",
      "default": 30,
      "maximum": 120,
      "minimum": 1
    },
    "from": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Origin station code"
    },
    "start_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First day of the span"
    }
  }
}

nearby_stations

Other railway stations within a radius of one station, nearest first. Useful when a place has no service of its own and the traveller needs to know what is reachable — the planner already does this internally, so reach for it only when somebody asks the question directly.

read-only

Argument	Type	Description
limit	integer
radius_km	integer
station_code*	string

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "station_code"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 40,
      "minimum": 1
    },
    "radius_km": {
      "type": "integer",
      "default": 40,
      "maximum": 150,
      "minimum": 1
    },
    "station_code": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1
    }
  }
}

next_confirmed_date

Search forward up to a month for the first date this route can actually be travelled with a confirmed berth — direct trains and one-change journeys together. Use it when a traveller is flexible about WHEN and the date they asked for is waitlisted. EXPENSIVE: it checks seats across dozens of trains and dates, so it is limited to a few calls an hour; for a single date use check_train_options instead.

read-only

Argument	Type	Description
to*	string	Destination station code
date*	string	The date to search forward FROM
from*	string	Origin station code
quota	string

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "from",
    "to",
    "date"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Destination station code"
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date to search forward FROM"
    },
    "from": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Origin station code"
    },
    "quota": {
      "enum": [
        "GN",
        "TQ",
        "PT",
        "LD",
        "SS"
      ],
      "type": "string",
      "default": "GN"
    }
  }
}

plan_journey

Every practical way to get from one place to another: direct trains with their fares per class, journeys with one change of train, flights, mixed train-and-flight itineraries, and GOVERNMENT BUSES from the state road transport corporations, priced from their own reservation systems. This is the whole answer in one call. Place ids come from find_place. Use it for bus questions too. On a large share of the corridors these corporations serve there is no through train at all — Mysuru to Mangaluru runs twenty-five buses a day and not one direct train — so a journey this tool answers with a bus is often the only through service that exists, not a second-best. Pass `train_class` when the traveller has named one ("3A", "sleeper") and every train is priced in it; leave it out and each train is priced in every class we have evidence it carries. Pass `modes: "trains_only"` when they have said train — do not ask them to choose otherwise, because the point of this planner is that they do not have to. Pass `arrive_by: true` when they named a time they must BE somewhere rather than a time they want to leave.

read-only

Argument	Type	Description
to*	string	Place id from find_place
date*	string	Travel date in IST. Today is allowed; the past is refused.
from*	string	Place id from find_place
limit	integer	How many of EACH kind to return. Raise it only if the traveller asks to see more.
modes

station_departures

Every train scheduled to call at a station, in departure order — the enquiry board, not a journey plan. Use plan_journey when somebody wants to get somewhere; use this when they are asking what leaves from here. Scheduled times only.

read-only

Argument	Type	Description
after	string	Only departures at or after this IST clock time, HH:MM
limit	integer
station_code*	string	Station code, e.g. CNB

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "station_code"
  ],
  "properties": {
    "after": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Only departures at or after this IST clock time, HH:MM"
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "station_code": {
      "type": "string",
      "maxLength": 12,
      "minLength": 1,
      "description": "Station code, e.g. CNB"
    }
  }
}

train_schedule

Every stop of one train with its scheduled arrival and departure, in order. Scheduled times only — this says nothing about where the train is today.

read-only

Argument	Type	Description
train_number*	string

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "train_number"
  ],
  "properties": {
    "train_number": {
      "type": "string",
      "pattern": "^\\d{4,6}$"
    }
  }
}

{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "from", "to", "date" ], "properties": { "to": { "type": "string", "maxLength": 80, "minLength": 2, "description": "Place id from find_place" }, "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Travel date in IST. Today is allowed; the past is refused." }, "from": { "type": "string", "maxLength": 80, "minLength": 2, "description": "Place id from find_place" }, "limit": { "type": "integer", "default": 8, "maximum": 20, "minimum": 1, "description": "How many of EACH kind to return. Raise it only if the traveller asks to see more." }, "modes": { "enum": [ "any", "trains_only", "flights_only" ], "type": "string", "default": "any", "description": "Restrict the answer. Default 'any' ranks trains, flights and government buses together — leave it out unless the traveller has actually named a mode. 'trains_only' and 'flights_only' both drop the buses." }, "quota": { "enum": [ "GN", "TQ", "PT", "LD", "SS" ], "type": "string", "default": "GN" }, "arrive_by": { "type": "boolean", "default": false, "description": "When true, `date` is the day they must ARRIVE, and journeys may depart the day before." }, "train_class": { "enum": [ "2S", "SL", "CC", "3E", "3A", "2A", "1A", "EC" ], "type": "string", "description": "Price every train in this class: 2S Second Sitting, SL Sleeper, CC AC Chair Car, 3E AC 3 Economy, 3A AC 3 Tier, 2A AC 2 Tier, 1A First AC, EC Executive Chair Car. Omit to price each train in every class we know it carries." }, "ask_preferences": { "type": "boolean", "default": true, "description": "Whether to ask the traveller for a travel class when they have not named one. Set false for automated or bulk use." }, "include_connections": { "enum": [ "auto", "always", "never" ], "type": "string", "default": "auto", "description": "Journeys with one change of train. 'auto' searches for them when direct trains are thin, which is when they matter; 'always' searches regardless and costs a few more seconds." } } }