Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Paytm Travel is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Discover and compare live Paytm flights and buses by fare, schedule, operator, stops, and amenities.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http paytm-travel-mcp https://travel.paytm.com/mcp/mcp
# 2 — ask your agent for something these tools do
# search_flights, get_flight_details, get_flight_review and 7 more
Paytm Travel costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http paytm-travel-mcp https://travel.paytm.com/mcp/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Searches live flights on Paytm and shows an interactive results card (airlines, logos, timings, stops, fares). Origin and destination are IATA codes (e.g. DEL, BOM, DXB) and dates are ISO (YYYY-MM-DD). A round trip uses trip_type='round_trip' with return_date. Filters: non_stop, airlines, max_price, time_slot, refundable; sort_by: best, cheapest or fastest. This is the tool for requests to show, f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Departure IATA code, e.g. "DEL". |
| destination | string | yes | Arrival IATA code, e.g. "DXB". |
| departure_date | string | yes | Outbound date as YYYY-MM-DD. |
| trip_type | string | no | "one_way" or "round_trip" (round_trip needs return_date). |
| return_date | no | Return date YYYY-MM-DD (required for round_trip). | |
| passengers | integer | no | Number of adult travellers (default 1). |
| children | integer | no | Number of child travellers (default 0). |
| infants | integer | no | Number of infant travellers (default 0). |
| cabin | string | no | economy | premium economy | business | first (default economy). |
| non_stop | boolean | no | Only non-stop flights. |
| airlines | no | Restrict to these airline names or codes, e.g. ["IndiGo","6E"]. | |
| max_price | no | Budget cap in INR. For one_way this is the per-flight fare; for round_trip it is the COMBINED both-legs total. | |
| time_slot | no | OUTBOUND departure bucket: early_morning [00:00, 06:00) | morning [06:00, 12:00) | afternoon [12:00, 18:00) | evening [18:00, 24:00). Applies to the outbound leg only. "early morning" is accepted. "ni | |
| return_time_slot | no | Same buckets, for the RETURN leg of a round trip. Omit to leave the return leg unfiltered by time. | |
| depart_after | no | Earliest outbound departure hour, e.g. 6 or "06:00" (inclusive). Use with depart_before for a narrow window that the coarse time_slot buckets cannot express. | |
| depart_before | no | Exclusive end — "09:00" means the last acceptable departure is 08:59. 9 and "09:00" are the same instant. "09:30" keeps 09:15. A window whose end is earlier than its start is rejected; this search doe | |
| return_depart_after | no | Earliest RETURN departure hour, e.g. "19:00". | |
| return_depart_before | no | Latest RETURN departure hour, exclusive. | |
| refundable | boolean | no | Only refundable fares. |
| sort_by | string | no | best | cheapest | fastest (default cheapest). |
Fare options and travel policies for one flight. Renders the Flight Details panel: multi-fare upsell comparison (Saver, Flexi, etc.) plus baggage, cancellation, and reschedule tabs. This is the source for flight details, fare options, upsell fares, baggage allowance, cancellation fees, reschedule fees, or policies for a specific flight, including right after search_flights or when the traveller ta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offer_token | string | yes | Offer token from search_flights — either the long signed token or the flight's short offerRef. Both resolve to the same offer. |
| return_offer_token | string | no | Optional return-leg token for a round trip, in either of the same two forms. |
Shows the Paytm flight details / review page for a selected fare: itinerary summary, fare breakdown (base, taxes, total), refundability, and a Book on Paytm Checkin link. The review call refreshes the fare before handoff. It is the step between choosing a fare and booking: requests to continue, review, see flight details for a chosen fare, or book after picking a fare in get_fare_family land here,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offer_token | string | yes | Offer token from search_flights / get_fare_family — either the long signed token or the short offerRef. |
| return_offer_token | string | no | Optional return-leg token for a round trip. |
| price | no | Selected onward fare in INR from the fare-family Continue tap. Omit when the user asked to review without picking a fare — the tool then uses the recommended branded fare. | |
| fare_name | string | no | Optional branded-fare name (Saver, Flexi, …) as a second match key when price is missing or no longer live. |
| return_price | no | Selected return fare in INR (round trip only). | |
| return_fare_name | string | no | Optional return-leg fare name. |
| trip_type | string | no | "oneway" (default) or "roundtrip". Set automatically when return_offer_token is present. |
Computes the combined round-trip fare for a chosen onward + return flight pair, reprices it, and returns the total plus a Paytm booking link. Used by the flight results card when both legs are selected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| onward_offer_token | string | yes | — |
| return_offer_token | string | yes | — |
Shows a Paytm fare calendar: the cheapest flight fare for every date in a range, so the traveller can spot the cheapest days to fly. Supports date-range queries and round trips. Origin and destination are IATA codes (e.g. DEL, BOM, DXB) and dates are ISO (YYYY-MM-DD). It answers cheapest *dates/days* and lists no individual flights; requests to show or find flights are served by search_flights. Fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin IATA code, e.g. "DEL". |
| destination | string | yes | Destination IATA code, e.g. "DXB". |
| start_date | string | yes | First date of the range, YYYY-MM-DD. |
| end_date | string | yes | Last date of the range, YYYY-MM-DD. |
| trip_type | string | no | "oneway" or "roundtrip" (roundtrip also returns the return leg). |
| cabin | string | no | economy | premium economy | business | first. |
| adults | integer | no | Adult travellers (default 1). |
| children | integer | no | Child travellers (default 0). |
| infants | integer | no | Infant travellers (default 0). |
Fare family / branded fare selector for ONE specific flight. Returns every fare the airline sells on that flight (Saver, Flexi, Flexi Plus, ...) with a single recommended pick and the reasons for it, scored on concrete rupee benefit per rupee of premium. It answers which fare to pick, fare families, branded fares, fare types, 'what do I get for more', or a comparison of fare options for a flight a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offer_token | string | yes | Offer token from search_flights — either the long signed token or the flight's short offerRef. Both resolve to the same offer. |
| return_offer_token | string | no | Optional return-leg token for a round trip, in either of the same two forms. |
Sends the results cards' interaction analytics to Paytm's first-party Signal ingest. The cards' analytics script calls this because the card sandbox cannot reach that ingest on its own. The server chooses the ingest endpoint and accepts a Signal analytics batch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| headers | object | yes | — |
| body | string | yes | — |
Searches live Paytm bus routes and shows an interactive results card (operator, bus type, timings, rating, seats left, price). One-way, domestic, search only -- no seat selection or booking happens in chat. REQUIRED ARGS (same posture as search_flights): source, destination, and date are ALL mandatory. source/destination are free-text city names (e.g. 'Bengaluru', 'Hyderabad'); date is YYYY-MM-DD.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | Departure city name, e.g. "Bengaluru". |
| destination | string | yes | Arrival city name, e.g. "Hyderabad". |
| date | string | yes | Travel date as YYYY-MM-DD. Mandatory — do not invent a date if the traveller omitted it; ask them first. |
| source_city_id | no | Resolved Paytm city id for source -- only pass this after a prior call returned needsDisambiguation with sourceCityOptions, using the id the traveller picked. | |
| destination_city_id | no | Same, for destination. | |
| bus_type | no | "AC" or "Non-AC" when the traveller only named climate, or a full type ("AC Sleeper", "AC Semi-Sleeper", "AC Seater", "Non-AC Sleeper", "Non-AC Semi-Sleeper", "Non-AC Seater"). | |
| time_slot | no | early_morning [00:00, 06:00) | morning [06:00, 12:00) | afternoon [12:00, 18:00) | evening [18:00, 24:00). "early morning" is accepted. "night" is rejected. There is no overnight slot. | |
| depart_after | no | Earliest departure, e.g. 18 or "18:00" (inclusive). 7, "7", and "07:00" are the same instant. | |
| depart_before | no | Exclusive end, e.g. 7 or "07:30". "4–7 AM" is depart_after="04:00", depart_before="07:00". "00:00" means the end of this day. A window whose end is earlier than its start (22:00 to 04:00) is rejected; | |
| operators | no | Restrict to these operator names. | |
| max_price | no | Budget cap in INR (per traveller, starting fare). | |
| min_rating | no | Minimum star rating (buses with under 15 ratings are excluded from this filter -- their rating isn't shown either). | |
| paytm_assured | boolean | no | Only Paytm Assured buses. |
| boarding_point | no | Restrict to buses with a matching boarding-point area. | |
| sort_by | string | no | recommended | cheapest | fastest | earliest | rating. |
Builds one differentiating line for each bus on the results card, from the search payload already fetched (no bus-details calls), using Azure OpenAI inside this server. An empty line is valid when nothing stands out. Used by the bus results card after it renders; it renders no card of its own. It prefers the search_context that search_buses returned, so no second search is needed, and re-fetches t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_refs | array | yes | — |
| source | string | yes | — |
| destination | string | yes | — |
| date | string | yes | — |
| cards | array | yes | — |
| search_context | no | — | |
| source_city_id | no | — | |
| destination_city_id | no | — | |
| bus_type | no | — | |
| time_slot | no | — | |
| depart_after | no | — | |
| depart_before | no | — | |
| operators | no | — | |
| max_price | no | — | |
| min_rating | no | — | |
| paytm_assured | boolean | no | — |
| boarding_point | no | — | |
| sort_by | string | no | — |
Shows the Bus Details sheet for one trip from search_buses: amenities (iconified), pickup and dropping points with times, cancellation-policy slabs, rating, and a Book on Paytm Checkin CTA. This is the source for amenities, boarding/dropping points, cancellation policy, or details for a specific bus, including a tap on a bus card in the widget. The tripRef from the card is enough, without a new se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_ref | string | yes | Opaque trip token from search_buses (tripRef on each card). |
| summary | string | no | Optional AI summary line already shown on the card, so the details sheet shows the same line. |
| booking_url | string | no | Optional Paytm Checkin seat URL from the search card (dweb). |
| booking_deeplink | string | no | Optional H5/mweb/app deeplink (paytmtr://bus-seat). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Paytm Travel or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.4.7.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Paytm Travel can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.