trivago

com.trivago.mcpPublished by mcp.trivago.comOfficial publisherv0.6.0Updated Oct 28, 2026

trivago's mcp server to find your ideal hotel and compare prices from multiple providers.

VerifiedStreamable HTTPWeb executableLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

trivago's remote MCP server lets an assistant search live hotel listings, compare prices across booking sites, and forecast monthly price trends for a…

What you can do
  • Search hotels and accommodation by destination or point of interest, with price, rating, amenities and a link per property
  • Search accommodation near coordinates such as a landmark, address, venue or neighborhood
  • Filter and configure results by date range, guests and rooms, star rating and guest rating
  • Forecast monthly price trends for a destination, with average, minimum and maximum nightly rates by star rating
When to use it
Useful when a user wants help finding or comparing hotels for a trip, anchoring a stay to a specific place, or planning when to travel based on how prices change through the year.
Requirements
A remote MCP endpoint; no package, environment variables or headers are declared. The manifest declares no authentication.
Before you install
Results are metasearch aggregates from third-party booking sites, and the price-trend tool is a forecast rather than live availability, so prices and availability should be confirmed before booking. No credentials are declared, but searches reveal travel destinations and dates to the service.

Installation

In SourceWeft

  1. Open trivago in the dashboard and add it to a workspace.
  2. 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/com.trivago.mcp%2Fmcp/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.

{
  "mcpServers": {
    "trivago": {
      "type": "http",
      "url": "https://mcp.trivago.com/mcp"
    }
  }
}

Tools

3

Version history

2
  1. v0.6.0LatestOct 21, 2026
  2. v0.5.0Sep 16, 2026

Score

72% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.