Travel · Remote MCP server
travelMCP Directory
Search MCP servers, agent skills and APIs for travel: hotel ID mapping, rates, rooms.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.omnitravel/travelmcp-directory- Version
- 1.0.0
- Status
- Active
- Category
- travel
- Transport
- Streamable HTTP
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- ai.omnitravel
- Namespace
- Namespace verified by the MCP Registry via the domain omnitravel.ai · how
- Listed under
- Hotels MCP servers
- Website
- omnitravel.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://omnitravel.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- travelmcp-directory 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
search_travel_tools,get_tool_details,list_categories - Checked on
- 2026-10-05
How to connect travelMCP Directory
travelMCP Directory is a remote MCP server: there is nothing to install. Its endpoint is https://omnitravel.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, omnitravel.ai, was checked for the files that tell AI systems about a site.
More travel servers
| Server | Runs |
|---|---|
| travel.artArt-tourism data for AI agents: biennales, art fairs, museums, layover itineraries with 2026 facts. | Remote · HTTPLive check: ✓ handshake |
| Traveler.mdA traveler's portable travel profile and trip plans. It remembers, it does not search or book. | Remote · HTTPLive check: sign-in required |
| TravelerLocal - China travel facts for foreign visitorsField-verified China travel facts for foreign visitors: booking walls, hotel registration, transit. | Remote · HTTPLive check: ✓ handshake |
| Travellers Group - Regional Australia HotelsVerified facts and direct-booking handoff for five Travellers Group hotels in regional Australia. | Remote · HTTPLive check: ✓ handshake |
| TravelMind MCPTravelMind: 8 MCP tools for travel (12306 trains, flights, hotels, geocode, planning, policy). | Remote · HTTPLive check: sign-in required |
| TravelMindsAI ConciergeGrounded, multilingual travel data + a cited travel concierge. 12+ languages, deep India coverage. | Remote · HTTPLive check: ✗ no handshake |
| TravelOwlPlan trips directly into TravelOwl from a conversation with Claude. | Remote · HTTPLive check: sign-in required |
| TravelpayoutsTravelpayouts MCP - wraps the Aviasales Flights Data API (travelpayouts.com) | Remote · HTTPLive check: ✓ handshake |