Travel World - MCP Server

Plan, search and book flights and hotels. Check out live flight status, special promotions, and local guides. Safe and secure checkout with Stripe Link.

Get access

Travel World is invite-only, so start here — the connect steps below only work once you’re in. If you were given an invite email, enter it under Who invited you? and your access unlocks the moment you join. Without one you go on the waitlist and we’ll let you in as places open.

Request early access

Already invited? Sign in →

Join the waitlist

Join the early-access list for your personal AI travel agent. Got an invite? Add your inviter’s email below to skip the queue and unlock beta access now.

Enter the email of the person who invited you to claim beta access and your own 2 invites. Leave blank to just join the general waitlist.

Connect

Remote (Streamable HTTP) server at https://travel.augworlds.ai/mcp. Sign in with your Travel World account — your client registers itself and runs the OAuth flow. There is no token to copy, no --header, and nothing to paste into chat.

Claude Code

Add the server:

Terminal

claude mcp add --transport http --scope user travel-world https://travel.augworlds.ai/mcp

Then, inside a Claude Code session:

  1. Type /mcp — a slash command in the session, not a shell command. (At a terminal prompt it just returns no such file or directory.)
  2. Choose travel-world → Authenticate. Your browser opens, you sign in, and the session comes back connected.

Keep --scope user. Without it the default local scope binds the server to whatever directory you ran the command in — it will look like it installed fine and then simply not be there in your next project.

Claude Desktop & claude.ai

  1. Settings → Connectors → Add custom connector.
  2. Paste https://travel.augworlds.ai/mcp and choose Connect.
  3. Sign in when prompted.

No CLI, no config file. Travel World is a remote server, so it belongs under Connectors — Local MCP Servers is a different list, for servers that run on your own machine.

Cursor

Add the server to ~/.cursor/mcp.json, then sign in when Cursor prompts you:

~/.cursor/mcp.json

{
  "mcpServers": {
    "travel-world": {
      "url": "https://travel.augworlds.ai/mcp"
    }
  }
}

Codex

Add the server to ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.travel_world]
url = "https://travel.augworlds.ai/mcp"
bearer_token_env_var = "TRAVEL_AW_MCP_TOKEN"

Codex authenticates with a service token rather than the browser sign-in — mint one below.

Other MCP clients

Any client with OAuth support needs only the URL — it discovers the rest from the server and prompts you to sign in. If your client does not do OAuth yet, use the service token below.

Requests are rate-limited per key; a burst returns HTTP 429 with a Retry-After header — back off and retry.

CI & service access (fallback)

For non-interactive callers — CI jobs, servers, scripts — where no human can complete a sign-in, a personal access token (tvl_ prefix) still works. Once you’re in the beta you mint one instantly at generate your MCP token. Prefer OAuth for anything you use interactively.

Read the token from an environment variable. Never commit it, and never paste it into a chat window — anything you type to an agent is model input.