← Plugin catalog
Travel

Byway Travel

Byway v1.0.1

Plan European rail trips

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Plan multi-city rail itineraries in Europe
  • Plan trips around fixed-date events
  • Show train legs, stays and a total trip price

Cost & access

The plugin plans and saves trips and takes no payments. Travellers book on Byway's website from the trip link.

Declared limitations

  • Booking and payment aren't supported
  • Flights and travel outside Europe aren't covered
  • Managing existing bookings isn't supported
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

Plan and save multi-stop rail itineraries across Europe, or a trip to a concert, festival or conference on fixed dates. Give a starting point and the places you want to visit, and Byway chooses the best route and returns the train legs, hotels, dates and a total price, with a link to the full trip. Trips are saved, not booked: nothing is paid for until the traveller books from the link. Some details, such as train times, may still need confirming.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 16, 2026. Last seen Nov 16, 2026.

Keywords

Files & skills

File archives

Plugin package6 files · 30.9 KBBrowse files →
Skill instructions
byway-travel4.24 KB

View saved version →

---
name: byway-travel
description: Plan European train trips with the Byway connector - city breaks, multi-city trips and trips to fixed-date events. Creates fully priced, fully bookable trips.
---

# Planning trips with Byway

Byway builds complete overland trips across Europe: the trains between places, a hotel at each stay, and a total price, saved as a trip the traveller can open, adjust and book. The Byway connector (the MCP server) does the planning, so a trip from it is real, current and bookable, whereas trips built purely from search are often guesses.

The connector has two tools:

- **buildTrip** builds and saves a trip and returns a link plus a summary of what was built.
- **listPlaces** looks up the place names Byway knows. You rarely need it.

If neither tool is available, the Byway connector isn't connected in this chat. Say so, and suggest the user turns it on.

## Building a trip

Call buildTrip straight away with what the user has told you. Plain city names work (case and accents don't matter), so don't call listPlaces first.

- **origin** is where the trip starts, usually a UK city such as London. If Byway rejects it as an origin, call listPlaces with `originsOnly=true` to see the choices.
- **stayPlaces** are the places to stay, up to 9. Byway chooses the order from its routing, so it may not keep the order the user gave, and it may add an overnight stop on a long journey.
- **finalDestination** makes the trip one-way. Leave it out for a trip that returns to the origin.
- **Dates** are YYYYMMDD. With no dates, Byway starts the trip about three months ahead and gives each stay 3 nights. If the user gives a length ("a week in Italy"), pass a start and end date.
- **tripTitle** is optional. A short title that fits the request ("Rome and Florence in spring") reads better than the default, which is the stay names.

A build takes up to a minute, so tell the user it's being planned rather than going quiet.

### Trips around an event

When the user has something fixed to get to, give all four event fields:

- **eventPlace**: the city the event is in.
- **eventStartDate**: the first night they stay there.
- **eventEndDate**: the day they check out, which is the morning after the last night. An event running 1 to 3 November with nights on the 1st, 2nd and 3rd gives `eventEndDate` 4 November.
- **eventNeedsAccommodation**: `false` if their hotel is already arranged (for example, the organiser provides it), otherwise `true`.

Other stays are fitted around the event. If one can't fit, Byway drops it and says so in the warnings.

## Telling the user about their trip

On success, the result's `summary` describes what was actually built. Use it rather than restating the request:

- `stays` lists each stay in order with its nights and dates. `chosen: false` marks an overnight stop Byway added on a long journey, which is worth pointing out.
- `items` lists every train (operator, stations, departure and arrival times) and stay in order.
- `totalPrice` with `currencyId` is the price of the whole trip. Individual items have no prices, so don't invent any.

Always mention anything in `warnings`, such as a stay dropped or moved to fit an event: the user needs to know their plan changed. Then give them the link (`url`) to see the full trip.

The trip is saved, not booked. Nothing has been paid for and no seats or rooms are held, so don't say it's booked.

Every trip is planned for two adults sharing one room, and the total price is for them. Before booking, the user can change the trip on the linked page: the number of nights, the travellers, the hotels, the rooms and the class of travel, and the price updates to match. So if they ask for something buildTrip can't set, like a trip for four or first class, build it anyway, then say what it was planned with and that they can change it on the trip page. The one thing neither buildTrip nor the trip page can change is the order of the stays, which Byway chooses, so don't promise a par

Preview of the first 4,000 characters. Read full instructions →

Release notes

First release. Plan multi-stop European rail trips, including trips around fixed-date events, with train legs, hotels and a total price, saved as a trip to view and book on Byway.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Byway
Keywords
See keywords
Declared availability
No country restrictions declaredDeclared regions; live availability may differ.
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Plan multi-city rail itineraries in Europe
  • Plan trips around fixed-date events
  • Show train legs, stays and a total trip price

Package observed Nov 16, 2026.

Technical details
First seen
Nov 16, 2026 · 18:00 UTC
Last seen
Nov 16, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6aec95c9b0e881919e3b89382370306a

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.