Omio MCP server for ChatGPT and Claude
Connect ChatGPT, Claude, Codex and Claude Code to Omio travel workflows through Cotlet.dev. Unofficial, not affiliated with Omio.
Connect
- Request access.
- Sign in to Omio in its Cotlet.dev Cloud Browser and enable it for agents.
- ChatGPT and Claude use
https://cotlet.dev/mcp/v1/connectwith Cotlet sign-in. Editors and scripts can usehttps://cotlet.dev/mcp/v1/omiowith a Cotlet API key.
claude mcp add --transport http cotlet-omio https://cotlet.dev/mcp/v1/omio --header "Authorization: Bearer $COTLET_API_KEY"
Travel workflows
The current integration page documents 16 hosted operations: 12 read and 4 write operations. Search trains, buses, flights and ferries; compare fares and refund conditions; find lower-priced travel dates; price round trips; read bookings; and manage saved travelers.
start_booking returns a checkout link. You review and pay on Omio yourself. Search results cover selected journeys and time windows, rather than the entire timetable. Extend supported windows with list_more_trips. Price-calendar figures can be some hours old; search for current fares before choosing a journey.
Local MCP bridge
This package is a stdlib-only MCP bridge to hosted Cotlet.dev. It requires a Cotlet account, an enabled Omio connection and a Cotlet API key. It does not run the separate self-hosted Omio implementation from the source repository.
Python 3.10 or newer:
pip install omio-mcp
export COTLET_API_KEY="your Cotlet API key"
omio-mcp
Configure your MCP client to launch omio-mcp with COTLET_API_KEY in its environment. The bridge exposes seven generic tools for guiding the browser connection, listing available operations, reading, writing, updating and deleting through the hosted service. These are wrappers for the hosted operations, not seven additional Omio features.
Get your key at https://cotlet.dev/app. Follow your console settings for approvals.
Links
Elastic License 2.0. See LICENSE.
Metadata
Release files for omio-mcp 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| omio_mcp-1.1.0.tar.gz | 6.8 kB | Without provenance | Details for omio_mcp-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omio_mcp-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for omio_mcp-1.1.0-py3-none-any.whl |
Total release size: 14.5 kB
Release files / omio_mcp-1.1.0.tar.gz
| Download URL | omio_mcp-1.1.0.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9fee2942ce5dbb3ecdd2c870eee067321babd67168eef3d96ab8bf66eef6cc0b
|
|
BLAKE2b-256 checksum How to use checksums |
122c66e17b6e632ac3a8e40699c81155104d9a096480a0f50479b69645b110bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / omio_mcp-1.1.0-py3-none-any.whl
| Download URL | omio_mcp-1.1.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56a154bf67c8bab0c506e3f2bbdbab2ea320fb735ea11ecf65e472ddb79c0f01
|
|
BLAKE2b-256 checksum How to use checksums |
9b5092709a42dc3bf1512dfb81415e994f70f46893b8eda7d50abada2bc10d94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for omio-mcp 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.