Omio by Cotlet

Omio API and MCP server: connect Omio to ChatGPT and Claude

Yes, ChatGPT, Claude and other AI agents can work in your Omio account. That includes Cursor, Codex, OpenClaw and any MCP client, plus automations in n8n, Make and Zapier. Ask in plain words, and the AI searches trains, buses and flights, compares fares and conditions, reads your bookings and saved travellers and prepares the checkout. It shows you what it will do first and sends nothing to other people until you say so.

As of November 2026, this repo is the missing piece: 16 Omio tools for AI assistants and scripts.

What you can ask

*Compare train, bus and flight from Berlin to Munich next Thursday by price and travel time.*

*Which day in the next three weeks is cheapest from Berlin to Munich, and what is the cheapest train that day?*

*Price a round trip Berlin to Munich, out on Friday morning and back on Sunday evening, with my BahnCard 50.*

*Reserve the cheapest refundable train from Berlin to Munich next Thursday for me and my saved companion, and send me the total and the checkout link.*

Two ways to get it

Cotlet is best for travellers, assistants and travel teams who want ChatGPT, Claude or another AI agent to work in Omio for them, with nothing to install.

[Start free at cotlet.dev →](https://cotlet.dev/signup?app=omio&utm_source=github&utm_medium=readme&utm_campaign=omio&utm_content=top-button)

Run it yourself

An Omio API and an Omio MCP server you run on your own computer, in Python, on the session of your own Google Chrome. All 16 Omio tools we run in production at Cotlet: places, train, bus, flight and ferry search, the cheapest day of a route, fares with their refund and exchange conditions, round trips, a booking up to the checkout link, Your Bookings and saved travelers.

Omio has no public API for your own account. Its Search API sits in the affiliate programme, for partners, and Your Bookings, saved travelers and checkout exist only on omio.com and in the Omio app. This repo gives you:

• MCP server for Claude Code, Claude Desktop, Cursor, Codex and any MCP client, over stdio or HTTP. Setup
• REST API on http://127.0.0.1:8787/api/v1/omio, with OpenAPI docs at /docs. Setup
• Python: call("search_trips", {"from": "Berlin", "to": "Munich", "date": "2026-11-19"}), plus 8 ready scripts in examples/.

Nothing here pays. start_booking reserves the fare and returns a checkout_url, and you pay on omio.com yourself.

Free for your own use, your own business included (license).

uv tool install omio-api-mcp                  # or: pip install omio-api-mcp

omio-mcp connect # reads your Omio session from Chrome omio-mcp call search_trips from=Berlin to=Munich date=2026-11-19 limit=5 claude mcp add omio -- uvx omio-api-mcp mcp

Contents

• Questions from Omio users
• How it works
• Requirements
• Install
• Connect your Chrome
• MCP server
• REST API
• Python and the example scripts
• All 16 tools
• Configuration
• Security and your Omio account
• Errors
• Self-hosted or hosted
• FAQ
• License

Questions from Omio users

Does Omio have an API? Not for your own account. Omio's affiliate programme lists a Search API for partners, and its app in ChatGPT searches trips. Your Bookings, saved travelers, fare conditions and checkout work only on omio.com and in the Omio app. This repo and Cotlet give you 16 Omio tools as a REST API and an MCP server.

Can I get a Omio API key? Not from Omio for your own account. With Cotlet you get your own API key that works with your Omio account, for scripts, n8n, Make, Zapier or any HTTP client. This repo needs no key: it runs on your computer, on your own Omio session.

Is there an official ChatGPT integration for Omio? Omio has a ChatGPT app that searches trips. It does not see your account. Cotlet connects your own Omio account to ChatGPT, Claude and other AI agents: your bookings, saved travellers and fare conditions.

How do I connect Omio to ChatGPT? Sign up at cotlet.dev, sign in to Omio once in your Cloud Browser there, and add Cotlet to ChatGPT, following the steps in your account. Then ask ChatGPT about your Omio like you would ask an assistant. ChatGPT needs a server on the internet, so this repo alone, running on your computer, does not connect to ChatGPT.

Can ChatGPT book Omio train tickets for me? Yes, with Cotlet, up to the payment. It searches and compares trips, checks fare conditions, fills in your saved travellers and stops at checkout, so you pay yourself.

Can AI see my Omio bookings? Yes, with Cotlet: upcoming and past bookings, tickets and their conditions, in plain words.

Can I automate Omio with Zapier, Make or n8n? Omio has no Zapier or Make app. With Cotlet, n8n, Make and Zapier can search trips and read your bookings.

Can I use it from my phone? Yes, with Cotlet: once it is set up, the ChatGPT and Claude apps on your phone can use Omio for you.

Do I need to be technical? For Cotlet, no: you sign in to Omio and add Cotlet to ChatGPT or Claude, with step-by-step instructions in your account. This repo is for people who are fine with Python and a terminal.

Is my Omio account safe? Yes. Neither Cotlet nor this repo sees or stores your Omio password. You sign in yourself, the way you always do, and the AI works on that signed-in session. Anything that reaches other people asks for your OK first: in Cotlet by default, here through your MCP client.

Is it free? This repo is free, also in your own business. Cotlet is free for 7 days with no card, then one-time credit packs from $29, no subscription. Pricing.

I manage Omio for several accounts or clients. Does that work? Yes, with Cotlet. Each Omio login gets its own connection. Write to contact@cotlet.dev and tell us how many accounts you manage.

How it works

AI agent (MCP) / script (REST, Python) ──▶ omio-mcp on your computer ──your Omio cookies──▶ www.omio.com

▲ omio-mcp connect ───────┘ reads them once from your Chrome (DevTools Protocol)

1. You sign in to Omio in your own Chrome, the way you always do (Omio mails you a 6-digit code).
2. omio-mcp connect attaches to that Chrome through the Chrome DevTools Protocol, reads the omio.com cookies and saves them to ~/.config/omio-api-mcp/session.json, readable by your user only. Omio has no password, and this code never sees your mailbox.
3. Every tool call is a request to the endpoints Omio's own web app calls on www.omio.com (search, GraphQL, bookings, passengers) with those cookies, sent with curl_cffi, which copies Chrome's TLS fingerprint. No headless browser runs.

Cloudflare guards www.omio.com. Its cf_clearance cookie, which connect reads along with the session, belongs to your Chrome and your network. So run the server on the same computer and connection as the Chrome you connected. If Omio shows a bot check, open omio.com in that Chrome and run omio-mcp connect again.

Omio's sign-in cookie lasts about a year. When Omio signs you out, the server reads the cookies from Chrome again, if Chrome is open with remote debugging on.

Requirements

• Python 3.11 or newer.
• Google Chrome 144 or newer, signed in to Omio. Any Chrome or Chromium works with a debugging port.
• macOS, Linux or Windows.
• An Omio account. A free traveler account is all the tools need.

Install

From PyPI:

uv tool install omio-api-mcp       # or: pipx install omio-api-mcp, or: pip install omio-api-mcp

omio-mcp --version

MCP clients can also run it with no install: uvx omio-api-mcp mcp.

From source:

git clone https://github.com/cotletdev/omio-api-mcp-server.git

cd omio-api-mcp-server python3 -m venv .venv . .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e . omio-mcp --version

With uv: uv venv && uv pip install -e ., then uv run omio-mcp ....

Setting it up with an AI agent (Claude Code, Codex, Cursor)? Open it in this folder and ask it to set up the repo: AGENTS.md tells it every step, and it asks you only for the steps in Chrome.

To update: uv tool upgrade omio-api-mcp (or pip install -U omio-api-mcp), from source git pull && pip install -e .. We copy every change of the hosted Omio tools into this repo.

Connect your Chrome

Option A: your everyday Chrome (recommended)

1. Open chrome://inspect/#remote-debugging in Chrome and switch remote debugging on. Chrome then accepts DevTools connections from programs on this computer, and asks you before each one.
2. Make sure you are signed in at omio.com (your name shows in the top right).
3. Run:

   omio-mcp connect

1. Chrome asks whether to allow the connection. Click Allow.

Saved 40 Omio cookies to /Users/you/.config/omio-api-mcp/session.json

Signed in to Omio as Ana Lopez (ana.lopez@example.com)

You can switch remote debugging off again afterwards. Leave it on if you want the server to pick up a new session by itself after Omio signs you out.

connect looks for Chrome's DevToolsActivePort file in the default profile folder. For Chrome Beta, Canary or a custom profile folder, pass --profile-dir " ".

Option B: a Chrome with a debugging port

Chrome does not open a debugging port on your default profile, so start a separate one, sign in to Omio there once, and connect to it:

# macOS

"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --remote-debugging-port=9222 --user-data-dir="$HOME/.chrome-omio"

Linux

google-chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.chrome-omio"

Windows

"C:\Program Files\Google\Chrome\Application\chro