# RailRoute journey planner

- Registry name: `in.railroute/journey-planner` · version 1.3.0
- Categories (automatic, keyword rules): Travel & booking, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=in.railroute%2Fjourney-planner
- Server page: https://mcpstation.net/s/in.railroute--journey-planner.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://www.railroute.in/api/mcp`

## Tools (as reported by the server, not verified)

- `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. Ty
- `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 whol
- `check\_train\_options`: 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
- `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.
- `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.
- `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.
- `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.
- `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 a

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html