What is a travel MCP server?

The Model Context Protocol is the open standard AI assistants and agents use to call external tools. A travel MCP server exposes travel capabilities as those tools. Dreamfare's server lets an agent create and edit real trips, plan itineraries, search stays and activities with live prices, discover places, import travel videos and share trips, all on the connected traveler's Dreamfare account.

Which AI clients work with it?

Claude (claude.ai, desktop and mobile, as a custom connector on every plan), ChatGPT (the Dreamfare Travel Assistant plugin), Claude Code, Cursor, VS Code and any MCP client that speaks Streamable HTTP. Claude and ChatGPT render Dreamfare's interactive trip cards; other clients get the same tools as text.

How does authentication work?

OAuth 2.1 with PKCE and dynamic client registration. The traveler signs in on dreamfare.app, the agent receives a bearer token scoped to that account, and the agent never sees a password. Access can be revoked from the client's settings at any time.

Does it search flights?

No. The server records and reads flights that are already part of a trip, including booking confirmations, but it does not search fares. Flight search is planned.

Does using the server cost anything?

Connecting is free and most tools are free to call. Video and text imports and the one-call planner spend the traveler's plan or credits, exactly as they do in the app, and the tool result says so when a plan is needed.

Can an agent book a trip?

Every bookable stop carries a tracked partner booking link and the agent can hand it to the traveler, mark a stop as booked, and file the confirmation on the trip. Payment happens on the partner's site, never inside the server.

Dreamfare MCP

Travel tools for AI agents

Dreamfare is an AI-native travel platform that turns travel inspiration into bookable trips. The Dreamfare MCP server exposes the same capabilities to AI agents: an AI travel agent built on Claude, ChatGPT, Cursor or your own code can create and edit real trips, plan itineraries, search stays and activities with live prices, discover places, import travel videos and hand the finished trip to the traveler and their crew.

Connect an agent Tool reference

Endpoint https://api.dreamfare.app/mcp · Registry app.dreamfare/mcp · 42 tools

What the server can do

Every card below is a group of shipped tools, read from the server's own tool list. Trips made through the server are ordinary Dreamfare trips: on the map, editable in the app, shareable with a crew.

Trip creation and editing

Create a trip from a day-by-day plan, read it back with stop ids, edit anything in one batched call, copy or delete it, and keep the packing list.

AI itinerary planning

Build a complete trip in one call with Dreamfare's own planner: real venues with opening hours, a stay, partner activities, and booking links.

plan_trip

Place discovery and research

Find real venues for a destination with ratings, pins and photos, then research one option in depth or compare a few side by side.

Hotel and stay search

Live stay inventory with all-in prices for a destination and date window, and a re-quote of every partner-priced stay already on a trip.

Activity and tour search

Bookable tours and experiences for a destination, attachable to a trip as a stop.

search_activities

Travel video and text import

Turn a TikTok, Instagram, YouTube, Facebook or Reddit link, or pasted notes, into real places with tips, then check the import's results.

Saved places and travel tips

The traveler's library: save a place for later, tidy folders, drop saved places into a trip with pins intact, and keep the tips notebook.

Collaboration and trip chat

Invite people to a trip, manage roles, read and post in the crew chat, and vote on stops.

Publishing and public trips

Publish a trip to a public dreamfare.app/p page and Explore, browse what other travelers published, and copy any of them.

Bookings, receipts and travel essentials

File a booking confirmation on the right stop, read the receipts on a trip, and get eSIM, rental car and transfer links for the destination.

Traveler profile

Read the connected account (profile, membership, credits, wallet) and update profile fields.

More tools

Tools the server ships that are not filed under a category yet.

Deliberately not exposed

Flight fare search (flights on a trip are recorded and read, not searched)
Payments, subscriptions and credit purchases
Media uploads, account deletion and sign-in
Follows, notifications and reviews

Connect an agent

One remote server, Streamable HTTP, stateless: every POST is a complete JSON-RPC exchange, so any client or replica can call it. Travelers connecting from ChatGPT or Claude should start at Use Dreamfare in ChatGPT and Claude.

Claude

Open Claude settings, then Connectors, then Add custom connector.
Name it Dreamfare and paste https://api.dreamfare.app/mcp as the URL.
Press Connect and sign in to a Dreamfare account. Every Claude plan can add it.

ChatGPT

Open ChatGPT settings, then Plugins.
Search for Dreamfare Travel Assistant and choose Connect.
Sign in to a Dreamfare account when asked, then ask to plan a trip.

Claude Code, Cursor, VS Code

Add a remote server. The first tool call opens the sign-in flow in a browser.

# Claude Code
claude mcp add --transport http dreamfare https://api.dreamfare.app/mcp

# Cursor (.cursor/mcp.json)
{ "mcpServers": { "dreamfare": { "url": "https://api.dreamfare.app/mcp" } } }

# VS Code (.vscode/mcp.json)
{ "servers": { "dreamfare": { "type": "http", "url": "https://api.dreamfare.app/mcp" } } }

Any MCP client

initialize, ping and tools/list answer anonymously, so a registry or a script can read the catalog before anyone signs in. Everything else needs the bearer token from the OAuth flow.

curl -X POST https://api.dreamfare.app/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Authentication and limits

OAuth 2.1 with PKCE and dynamic client registration (RFC 7591). Register as a public client; token exchange needs no client secret.
Discovery at https://api.dreamfare.app/.well-known/oauth-authorization-server and https://api.dreamfare.app/.well-known/oauth-protected-resource. An unauthenticated tool call returns 401 with a WWW-Authenticate header that names the resource metadata, which is how clients find the flow.
Scope: the token acts only on the traveler who signed in, with the same permissions they have in the app. Shared trips respect crew roles.
Rate limit: 120 requests per minute per client. Responses are JSON; no SSE stream and no session id to keep.
Money at this boundary is in major units of the stated ISO currency (a night at 120 USD is 120); the app stores minor units.

Prompts that work

The same requests a traveler types in chat, each answered with an interactive trip card in Claude and ChatGPT.

Plan 5 days in Tokyo for late April with a mix of food and temples, then save it to Dreamfare.
Import this TikTok and tell me which places are worth a day trip: <paste link>
Find a hotel in Kyoto for May 10 to 12 under $200 a night and add the best one to my trip.
What is still unbooked on my Lisbon trip? Give me the booking links.
Make an invite link so a friend can edit my Lisbon trip, then post in the trip chat that dinner is booked.
Show me trips other travelers published for Portugal, and copy the Algarve one into my plans.

Tool flows for agents

Typical call sequences. Read a trip after any write: stops are enriched with pins, photos and booking links a few seconds later.

From a prompt to a bookable trip
create_trip→search_stays→add_option_to_trip→get_trip→share_trip
From a travel video to itinerary stops
import_video→get_import→add_saved_places_to_trip→get_trip
Start from someone else's itinerary
explore_trips→copy_trip→edit_trip→invite_to_trip

Questions

What is a travel MCP server?: The Model Context Protocol is the open standard AI assistants and agents use to call external tools. A travel MCP server exposes travel capabilities as those tools. Dreamfare's server lets an agent create and edit real trips, plan itineraries, search stays and activities with live prices, discover places, import travel videos and share trips, all on the connected traveler's Dreamfare account.
Which AI clients work with it?: Claude (claude.ai, desktop and mobile, as a custom connector on every plan), ChatGPT (the Dreamfare Travel Assistant plugin), Claude Code, Cursor, VS Code and any MCP client that speaks Streamable HTTP. Claude and ChatGPT render Dreamfare's interactive trip cards; other clients get the same tools as text.
How does authentication work?: OAuth 2.1 with PKCE and dynamic client registration. The traveler signs in on dreamfare.app, the agent receives a bearer token scoped to that account, and the agent never sees a password. Access can be revoked from the client's settings at any time.
Does it search flights?: No. The server records and reads flights that are already part of a trip, including booking confirmations, but it does not search fares. Flight search is planned.
Does using the server cost anything?: Connecting is free and most tools are free to call. Video and text imports and the one-call planner spend the traveler's plan or credits, exactly as they do in the app, and the tool result says so when a plan is needed.
Can an agent book a trip?: Every bookable stop carries a tracked partner booking link and the agent can hand it to the traveler, mark a stop as booked, and file the confirmation on the trip. Payment happens on the partner's site, never inside the server.