Omio MCP Server
Search trips, read fares and start a booking up to checkout in Omio.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/omio'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Omio API and MCP server: Let your AI agent prepare your Omio bookings.
Omio has no API for your own account and no MCP server you can add to an agent (checked 24 Oct 2026). Its official ChatGPT app searches and compares trips, and nothing official reads the fare rules, your saved travelers or Your Bookings, or starts a checkout for an agent. Cotlet runs 16 Omio tools hosted, over MCP for agents and REST for scripts.
Compare Omio journeys and fares with an AI agent, n8n, Make or a script. Use MCP for agent requests or REST for your travel workflow.
- Free 7-day trial, no card
- Unofficial, not affiliated with Omio
- Page: https://cotlet.dev/integrations/omio-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Omio. Omio is a trademark of its owner. If Omio's own integrations cover what you need, use them first.
What can you automate in Omio?
- Compare train, bus and flight
- Find the cheapest day
- Read refund and change rules
- Price a round trip
- Reserve and get the checkout link
- Keep saved travelers current
Does Omio have an MCP server or an API?
- The Omio app in ChatGPT launched on 14 Apr 2026. It searches trains, buses, flights and ferries in 46 countries; its listing says nothing about fare rules, saved travelers or Your Bookings, and it runs in ChatGPT only.
- The Search API belongs to the affiliate programme. Partners earn commission "for each redirect made to our booking page", so it sends travelers to Omio and never touches their account.
- No Zapier app, no n8n node, no Claude connector and no Omio MCP server on GitHub or in the MCP Registry.
| What you need | Omio app in ChatGPT | GitHub train MCP server | Cotlet |
|---|---|---|---|
| Search trains, buses, flights and ferries | Yes | Trains, not Omio | Yes |
| Fare rules: refund, exchange, conditions | Not listed | No | Yes |
| Saved travelers and discount cards | Not listed | No | Yes |
| Reserve and hand you a checkout link | Not stated | Booking link only | Yes, you pay |
| Works in Claude, Cursor and scripts | ChatGPT only | On your computer | Yes, hosted |
| Fixed for you when Omio changes | Yes | No | Yes |
Checked 24 Oct 2026. Sources: Omio app in ChatGPT, Omio launches in ChatGPT (press release, 14 Apr 2026), Omio Affiliate Programme, Omio Terms of Use, Omio Help: What is the service fee?, Omio Help: the price changed before I finished booking
How does Cotlet connect to Omio?
- Sign in to Omio. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never save your Omio password, and no tool pays: you pay at the Omio checkout link.
Connect Omio to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Turn on Omio for agents. Create a Cotlet account, sign in to Omio in its Cloud Browser and press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1/omio in the MCP or connector settings of your agent.
- Sign in or use a key. Chat apps ask you to sign in to Cotlet. Editors and scripts use an API key from the console.
One connection carries every app you enable, Omio among them. If you enabled Omio after connecting, refresh the connector so your agent sees the new tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1/omio \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1/omio",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1/omio"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: omio_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: omio_write
How to use the Omio REST API
Create your Cotlet API key
Create a Cotlet API key with access to Omio and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Sign in to your Omio account in its Cotlet Cloud Browser and enable the app for agents. Use a Cotlet key for REST; no separate agent connection is required.
Make your first Omio API request
REST:
curl "https://cotlet.dev/api/v1/omio/trips/search?from=Berlin&to=Munich&date=2026-11-17&limit=2" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read journeys and extend the search window
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "omio",
"tool": "search_trips",
"result": {
"search_id": "E3B02A2F5BF1045CD90E06B981AD2E45C",
"complete": true,
"trips": [
{
"trip_id": "E3B02A2F5BF1045CD90E06B981AD2E45C.-1936373539.1524867295158618159.train",
"mode": "train",
"operator": "Deutsche Bahn",
"departs": "2026-11-17T10:37:00.000+01:00",
"arrives": "2026-11-17T15:20:00.000+01:00",
"price": {
"amount": 86,
"currency": "EUR"
}
}
],
"total": 1
}
}
Replace the route and date with your journey. Read result.trips; result.total counts collected results before the requested limit, not every departure that day.
Search returns at most 100 selected results per call, with a default of 20. complete means the search modes responded, not that the whole day's timetable was covered.
Inspect the per-mode window flags. While can_extend_later is true, call list_more_trips with search_id, direction=later and a supported mode to read newly appeared journeys.
This is time-window extension, not cursor pagination. Searches remain usable for two hours; preserve the search ID and compare journey IDs and fares.
Read workflows do not buy tickets. start_booking hands you a checkout link so you can review and pay yourself.
Omio workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Run search_trips for a chosen route and date, extend supported windows and write a fare digest to your chosen sheet. |
| Make | HTTP > Make a request | Read get_trip for shortlisted journeys and prepare a comparison of fares and travel options. |
| Python or Node.js | REST API | Combine get_price_calendar, outbound search and list_return_trips into a round-trip planning shortlist. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Omio; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Omio API endpoints and MCP tools
Places and prices
The price calendar shows the lowest one-way price per day from recent searches, so a price can be some hours old.
- Search places (
search_places, read): Cities, train and bus stations, airports and ferry ports Omio knows, by name. - List discount cards (
list_discount_cards, read): Rail and coach discount cards Omio prices in, such as BahnCard or Railcards, by operator. - Get price calendar (
get_price_calendar, read): Cheapest one-way price per day and mode between two places, for up to a month.
Search and fares
Travel companies set the prices, and a price can move between the search and the payment.
- Search trips (
search_trips, read): Trains, buses, flights and ferries between two places on a date, with times, duration, changes, operator and price. - List more trips (
list_more_trips, read): Load later or earlier departures of a search's trains beyond the time window search_trips returned. - List return trips (
list_return_trips, read): Return legs Omio offers with one outbound leg of a round-trip search, with the round-trip price. - Get trip (
get_trip, read): Legs of one trip and its fare options with their conditions: class, price, refundable, exchangeable.
Start a booking
Stops before payment. Omio holds the seats for about 15 minutes, and you pay at checkout_url.
- Start booking (
start_booking, write): Reserve fares with the travelers' names and get the price breakdown and a checkout link. Pays nothing: the person finishes payment at checkout_url. - Get booking (
get_booking, read): Journey, travelers, fare conditions, status and price of one booking, paid or not yet paid.
Account and travelers
Saved travelers fill later bookings. Payment methods show the kind and brand, never numbers.
- Get account (
get_account, read): The signed-in Omio account: name, email, when it was made and its marketing email setting. - List bookings (
list_bookings, read): Bookings from Your Bookings with route, departure, operator and status. - List payment methods (
list_payment_methods, read): Payment methods saved on the account, by type and brand. Never card numbers. - List passengers (
list_passengers, read): Travelers saved on the account, the account holder first, with their details and discount cards. - Add passenger (
add_passenger, write): Save a traveler on the account so bookings can use their details. - Update passenger (
update_passenger, write): Change a saved traveler's details or discount cards, including the account holder's own. - Delete passenger (
delete_passenger, write): Remove a saved traveler from the account. The account holder cannot be removed.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/omio-api-mcp-server#tools
Who can see my Omio session, and how do I revoke it?
- What we store. Your signed-in Omio profile, encrypted with AES-256-GCM in Finland. No password.
- What your agent gets. The 16 Omio tools. Never the cookie or the login.
- What the session sees. What Your Bookings and Passenger details show: trips, travelers' names and dates of birth, prices.
- What no tool touches. Your password, the account email, card numbers and account deletion.
- If Omio signs you out. Your agent gets a link to sign in again. We never sign in for you.
- How to cut access. Disable Omio for agents, reset its browser or delete the key. The next call is refused.
A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Payment, undo and mistakes
- Finds the fare. Searches, then reads the fare rules: refundable, exchangeable, price for all travelers.
- Fills in the travelers. Names from you or from the travelers saved in the account.
- Stops before payment. Reserves the seats for about 15 minutes and returns the total and checkout_url.
- You pay. Open the link in a browser signed in to your Omio account, review the booking and pay, or leave it.
| Action | Undo |
|---|---|
| Start a booking | Leave it unpaid. The reservation lapses after about 15 minutes |
| Add a traveler | delete_passenger removes the traveler again |
| Change a traveler | update_passenger again; discount_cards replaces the saved cards |
| Delete a traveler | add_passenger saves them again; past bookings keep their travelers |
4 of 16 tools write: start_booking and the three traveler tools. None charges money or sends anything to anyone. The other 12 only read. Changing and cancelling a paid ticket are not built.
MCP call:
{
"name": "search_trips",
"arguments": {
"from": "Berlin",
"to": "Munich",
"date": "2026-11-17",
"modes": [
"train"
],
"limit": 1
}
}
REST:
curl "https://cotlet.dev/api/v1/omio/trips/search?from=Berlin&to=Munich&date=2026-11-17&modes=train&limit=1" \
-H "Authorization: Bearer $COTLET_API_KEY"
Tool output:
{
"search_id": "E3B02A2F5BF1045CD90E06B981AD2E45C",
"from": {
"place_id": "376217",
"name": "Berlin"
},
"to": {
"place_id": "376946",
"name": "Munich"
},
"date": "2026-11-17",
"return_date": null,
"complete": true,
"trips": [
{
"trip_id": "E3B02A2F5BF1045CD90E06B981AD2E45C.-1936373539.1524867295158618159.train",
"mode": "train",
"operator": "Deutsche Bahn",
"from": "Berlin Hbf",
"to": "Munich Hbf",
"departs": "2026-11-17T10:37:00.000+01:00",
"arrives": "2026-11-17T15:20:00.000+01:00",
"duration": "4h 43m",
"duration_minutes": 283,
"changes": 0,
"services": [
"ICE 1007"
],
"price": {
"amount": 86,
"currency": "EUR"
},
"bookable_on_omio": true
}
],
"total": 1
}
REST under /api/v1/omio takes the same tools from scripts and cron jobs, with the same key and price. The tools table lists the REST path of each tool.
How much does the Omio MCP server cost?
About $13 a month for someone who starts about six bookings a month, 2,200 credits. Tickets and Omio's fees are still paid in Omio.
| Job | Calls | Credits |
|---|---|---|
| Search and start a booking | 7 × 6 | 420 |
| Compare modes, no booking | 3 × 4 | 120 |
| Cheapest day, weekly | 2 × 4 | 80 |
| Price a round trip | 4 × 2 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,200 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Omio plan needed, a free account works
Omio publishes no figure for trips per account, so the month is our example: six bookings started, four comparisons, four calendar checks and two round trips. The browser is most of the bill. Dollars at the $29 pack rate.
Omio MCP server on GitHub, in ChatGPT or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Omio app in ChatGPT | Official and free. Searches and compares trips across 2,300+ travel companies. | Runs in ChatGPT only; its listing names no Your Bookings, changes or refunds. |
| oliver-virt/european-trains-mcp | MIT, 1 star. Train search with prices and a booking link on the Deutsche Bahn network, plus disruptions. | Deutsche Bahn data, not Omio; prices only on DB trains; last commit 4 Apr 2026. |
| eMelgooG/trainline-mcp | MIT, 0 stars. Trainline journeys and a price calendar. | Trainline, not Omio, and search only; last commit 20 Apr 2026. |
| Omio Scrapper on Apify | Playwright scrape of Omio search results by route and date. | Marked deprecated. Another Omio scraper there moved to Virail after Omio's Cloudflare blocked it. |
If you only want to compare routes in a chat, Omio's own app in ChatGPT does it for free. A GitHub train server suits a script that needs Deutsche Bahn or Trainline times. Cotlet is for when the agent has to work in your Omio account: read the fare rules, use your saved travelers and cards, and reserve the trip so you only have to pay.
Run our Omio MCP server on your own computer
All 16 Omio tools are also public on GitHub, as an MCP server and REST API in Python. It reads your session from your own Chrome, so you can try it on your Omio account and see how each tool talks to www.omio.com. It is a trimmed version of what runs on cotlet.dev, free to use in your own business.
- Free for personal use, learning and testing
- Works while your computer is on and Chrome is signed in to Omio
- Run it next to the Chrome you signed in with, because Omio's Cloudflare checks your network
- License Elastic 2.0: free in your own business; ChatGPT, your phone and 24/7 runs need hosted Cotlet
- Code: https://github.com/cotletdev/omio-api-mcp-server
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), and has worked since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Omio tools.
Omio API and MCP: questions
Can I use the Omio API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Sign up free at https://cotlet.dev, open Omio under Integrations in the console and sign in to Omio in its Cloud Browser. The free trial starts when you sign up and needs no card.
How do I connect Omio to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Omio once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Omio account through Cotlet, in their phone apps too.
What can ChatGPT do in Omio?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Omio: compare train, bus and flight options; find the cheapest day to travel; start a booking and get the checkout link. You ask in plain words, and anything that reaches other people waits for your OK first.
Does my agent pay for the ticket?
No. start_booking reserves the fares with the travelers' names and stops before payment: no payment method is chosen and nothing is charged. It returns the price breakdown, the total and checkout_url. You open that link in a browser signed in to your Omio account, review the booking and pay there. Omio holds the seats for about 15 minutes (reserved_until); after that the reservation lapses by itself.
What can it not do yet?
It does not pay, and it does not read, change or cancel a paid booking: there is no tool for tickets, exchanging a departure, cancelling or refunds. Seat choice, Omio Flex, vouchers and Omio Pass are not built either. There is no tool to delete a started booking. list_bookings is built but has not been checked against a paid booking, and list_more_trips widens outbound legs only, not the return legs of a round trip.
What if the fare needs more than a name?
Some fares ask for a date of birth, an ID document or a phone number. start_booking then fills in what it can, lists the rest in missing_details and returns a checkout_url that opens the passenger details page, so you complete them there before paying.
Which tools change something in my account?
add_passenger, update_passenger and delete_passenger edit the travelers saved under Passenger details, and start_booking creates an unpaid reservation. Nobody is told and nothing is charged. The account holder cannot be deleted. No tool touches your password, email or saved payment methods; list_payment_methods shows only the kind and card brand, never numbers.
Can it use my rail discount card?
Yes, for prices. list_discount_cards lists the cards Omio prices in, such as BahnCard. Give a traveler's card to search_trips in passengers and the prices include the discount. Omio applies a card only when it is selected for that traveler before the booking is completed.
Why can the price differ at checkout?
Travel companies set the prices and update them in real time. get_trip refreshes the fares with the operator, and start_booking returns the total as Omio now shows it, with its service fee as a separate line. If the operator moved the price in between, the status is price_change and the total is the new price.
How do I sign in to Omio?
In your own Cloud Browser, on omio.com: Omio asks for your email and sends a code, with no password. Cotlet keeps that session alive between calls. If Omio logs you out, your agent gets a link to sign in again.
Why not just use the Omio app in ChatGPT?
For comparing routes in ChatGPT it is the simpler choice, and it is free. Use Cotlet when you want the refund and change rules of each fare, your saved travelers and discount cards, or the same job from Claude, Cursor or a script.
Will I pay Omio's service fee on agent bookings?
The same as by hand. Omio sets the fee per booking, by trip, platform and dates, and some bookings have none. start_booking returns the fee as its own line in the price breakdown, before you pay.
Can my agent book as a guest?
No. Omio allows guest checkout, but the tools work in the account you signed in to, so every reservation is made in that account.
Is the MCP server different from the REST API?
Only in how you call it. Both have the same 16 tools, inputs and answers, under one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.
Is Cotlet affiliated with Omio?
No. Cotlet is independent and not affiliated with Omio.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.