What is a travel MCP server?

Last verified

A travel MCP server is a service that exposes travel actions, such as searching, planning, editing or booking trips, as Model Context Protocol tools an AI assistant can call. Servers differ mainly in whether they only search inventory, like flights or hotels, or manage a persistent trip the traveller keeps editing.

Start planning free →

How it works

  1. Discover. The assistant lists the server's tools, each with a name, a description and a JSON input schema.
  2. Authorize. The user grants the assistant scoped access, ideally without sharing a password.
  3. Call. The assistant sends a tool name and arguments and reads the structured result.
  4. Persist. For trip-management servers, the result is stored, so the next session continues the same trip.

How Goyondo implements it

Goyondo runs as a local MCP server, goyondo-mcp, that exposes 40 tools for persistent trips, itineraries, booking records and group plans, with sign-in through the OAuth device flow. It does not search live inventory, and there is no remote MCP endpoint yet. Adding it to Claude Code takes one command:

claude mcp add goyondo -- npx -y goyondo-mcp

Frequently asked questions

Is Goyondo a local or remote MCP server?
Local. goyondo-mcp runs over stdio next to clients such as Claude Desktop, Claude Code, Cursor and Codex. Web and mobile apps that need a remote MCP connector, such as claude.ai and ChatGPT, cannot connect yet.
Can a travel MCP server book trips?
Some search or book inventory. Goyondo does not: it records bookings you made elsewhere and focuses on the trip itself, including itineraries, edits and group alignment.
How does an assistant sign in?
With the OAuth device flow (RFC 8628). The assistant requests a code, the user approves it at goyondo.run/connect, and the assistant polls for a scoped key.