RZD Tickets MCP

What RZD Tickets MCP MCP server does

RZD Tickets MCP MCP server exposes read-only access to train pricing and availability data from the RZD ticket website. It helps an agent identify stations, find trains for a route and date, inspect carriage-level availability, and return matching seats according to practical constraints.

The server can distinguish lower, upper, side, and other places, look for a lower-plus-upper pair in one compartment, apply price and minimum-seat filters, and optionally include accessible places. It also returns the official RZD URL for completing the process manually. No account access or transaction operation is provided.

Tools and capabilities

Available MCP tools include:

• rzd_station_suggest finds a station’s nodeId and expressCode from its name.
• rzd_search_trains lists matching trains, prices, carriage groups, and an RZD link.
• rzd_train_cars retrieves carriage pricing details, seat information, upper/lower statistics, and image metadata.
• rzd_find_places returns only seats that satisfy the supplied filters.
• rzd_checkout_url creates an official RZD URL for manual checkout.
• rzd_parse_search_url reads parameters from an RZD search URL.
• rzd_service_classes explains service-class codes using information returned by RZD.

Search filters can include train numbers, departure-time windows, carriage type such as coupe or platz, raw service codes, seat type, pair requirements, side-seat and accessible-seat inclusion, maximum price, and minimum available places. Image retrieval can be requested when RZD reports that a carriage has images.

How it works

RZD Tickets MCP MCP server runs as an MCP stdio process and queries the read-only pricing endpoints used by the RZD web application. It uses browser-like request headers and reports upstream errors rather than hiding changes in the RZD response format.

Carriage image data includes availability flags, scheme and carrier information, and thumbnail or full-size URLs when the gallery endpoint responds. RZD does not provide images for every carriage, so the result can state why images were unavailable instead of fabricating them.

Service classes remain raw RZD codes rather than a fixed local enum. Results may include a title, tags, an official transcript, and a display description; agents should retain the original code and rely on the transcript when an exact interpretation is needed.

Setup and configuration

For a local checkout, install dependencies and build the project:

git clone git@github.com:ex3lite/mcp_rzd_tickets.git
cd mcp_rzd_tickets
npm install
npm run build
node dist/mcp.js

The published npm package can be started with npx -y mcp-rzd-tickets, which avoids cloning and building the repository. The server can be registered in Claude Desktop, Cursor, Windsurf, Cline, Roo Code, Continue, Claude Code, or Codex using each client’s MCP configuration. A local build can instead launch node with the absolute path to dist/mcp.js.

RZD_TIMEOUT_MS controls request timeout and defaults to 20000. RZD_PROXY_URL optionally selects an HTTP, HTTPS, SOCKS4, or SOCKS5 proxy. Without that variable, requests go directly to RZD.

Limitations and notes

RZD Tickets MCP MCP server is read-only. It does not authenticate, reserve tickets, create a hold, process payment, cancel an order, or change an RZD personal account. Booking must be completed by the user through the returned official link.

The upstream RZD web endpoints are private implementation details and may change without notice. Availability, pricing, service-class text, and wagon photos depend on what RZD returns at request time. Photo galleries are not guaranteed for every carriage, and a changed RZD payload may cause a visible tool error.