Dream Trip

app.thedreamtripPublished by thedreamtrip.appOfficial publisherv1.0.0Updated Nov 1, 2026

Your saved travel places, lists and trips. Plan day-by-day itineraries that land in Dream Trip.

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that connects an assistant to Dream Trip's saved travel places, lists and trips so it can plan day-by-day itineraries.

What you can do
  • Access saved travel places, lists and trips in a Dream Trip account.
  • Plan day-by-day itineraries that are saved back into Dream Trip.
  • No individual tools are documented in the listing, so the exact operations are not described.
When to use it
Useful when you want an assistant to work with your own Dream Trip travel data, for example drafting a day-by-day itinerary from places you have already saved and putting it into your account.
Requirements
A remote endpoint at the provider's site, reached over streamable HTTP; no local package or runtime is needed. An OAuth sign-in to a Dream Trip account is required. No environment variables or headers are declared.
Before you install
The server reads and writes personal travel data in your Dream Trip account, and itineraries it plans are added to that account. Access is granted through OAuth, so review the permissions requested at sign-in. The listing does not document which tools exist or what they change.

Installation

In SourceWeft

  1. Open Dream Trip in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.thedreamtrip%2Fdream-trip/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dream-trip": {
      "type": "http",
      "url": "https://www.thedreamtrip.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.