trivago
by trivago
trivago's hotel metasearch MCP server exposes 2 read-only accommodation search tools with no sign-in — one by destination name, one by coordinates. Both are annotated idempotentHint false. Verified live 2026-08-18.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect trivago via MCP
https://mcp.trivago.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect trivago once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman Studiotrivago Tools & Capabilities (2)
Search for accommodations and hotels using coordinates on trivago. Use this tool when you want to find accommodations near a specific location (landmark, neighborhood, or address). Additional Information: {"knownInformation":{"currentYear":"2026","today":"2026-08-17"}}
Search for accommodations and hotels by destination or point of interest on trivago. Additional Information: {"knownInformation":{"currentYear":"2026","today":"2026-08-17"}}
Read from the server on 2026-08-18, including each tool's own safety annotations.
Limits
- No booking, no payment, no availability hold. Both tools are read-only. The connector produces a shortlist with links; the reservation happens on the provider's site.
- Two tools, and they do one job. There is no hotel-detail lookup, no review-text tool, no flights and no experiences. The only choice is whether you name the place or give coordinates.
idempotentHint: falseon both tools, stated by trivago. Repeat calls are not guaranteed to return the same results. Do not cache a result and present it as current pricing.- The documentation's example call is wrong. trivago's docs page shows
search_hotelswithdestination,check_in,check_outandguests. No such tool exists on the server; take names and parameters fromtools/list. - Locale defaults to the US market silently.
countrydefaults toUS,currencytoUSDandlanguagetoEN_US. The schema sayscountrychanges pricing and content, not just display. - Date validation lives in prose, not in the schema.
arrivalanddepartureare typed as plain strings with noformatorpattern. The rules that arrival be future-dated and precede departure are instructions in the descriptions, addressed to the model. - The
roomsconstraint is also prose-only. The schema says rooms must not exceed the number of adults; no structural constraint enforces it. - The tool descriptions embed a hard-coded date. Both carried a context block naming 2026-08-17 as "today" when we read them. That value is baked into the description text and will drift from the real date between deployments.
- No prompts. The server does not declare the capability;
prompts/listreturns-32601prompts not supported. - No map without MCP Apps. The single resource is an
mcp-appwidget. A client that does not implement the extension gets the structured tool output without the map. - No published rate limit. Neither trivago's documentation page nor the handshake states a request ceiling, and we observed no
429. We make no claim about one. - No published pricing, coverage or savings figures. trivago's docs page carries illustrative hotel cards with prices and a "compares 100s of sites" line in its marketing copy. Those are promotional statements on a landing page rather than documented figures about the connector, and we cite none of them as facts about what a search returns.
- The privacy policy URL did not resolve for us. Anthropic's directory publishes
https://www.trivago.com/en-US/sp/privacy-policy; that URL returned HTTP 403 to our client on 2026-08-18, so nothing on it is cited here. works_withomits Claude API. The directory lists Claude, Claude Code and Claude Desktop only.- We called no tool. Our probe was
initialize,tools/list,prompts/list,resources/list,resources/templates/listand oneresources/read. Every behavioural claim above comes from the schemas, the resource, the directory or trivago's documentation page.
Frequently asked questions
No. We opened an anonymous handshake against the endpoint on 2026-08-18 and the server returned both tool definitions and its resource listing without a credential or an authentication challenge. trivago's own documentation page says the same thing in its own words, describing setup as needing no API keys and no configuration. Anthropic's directory records the connector as no-auth.
Because trivago states explicitly that a repeated call is not guaranteed to return the same result. This is a positive claim, not a missing annotation — both tools carry all four safety hints and set this one to false deliberately. It is defensible for a metasearch: live rates and availability across partner sites genuinely move between two identical queries minutes apart.
No. Both tools are annotated readOnlyHint true and destructiveHint false, and neither schema accepts a guest name, a payment method or a reservation instruction. The connector compares accommodations and returns a trivago URL for each result. Booking happens on the provider's own site after you follow that link, exactly as it does on trivago's website.
How you name the place. trivago-accommodation-search takes a query string — a destination or point of interest — while trivago-accommodation-radius-search takes latitude and longitude. The radius tool's description says to use it near a specific landmark, neighbourhood or address, and its coordinate fields warn that they mean the search target, not the user's own location.
Three for each tool, and dates are always two of them. trivago-accommodation-search requires query, arrival and departure. trivago-accommodation-radius-search requires latitude, longitude, arrival and departure. Both dates use YYYY-MM-DD format, arrival must be in the future, and departure must be after arrival — the schemas tell the model to warn the user when either rule fails.
Only if you ask. Both tools default country to US, currency to USD and language to EN_US regardless of where you are. The schema says the country code determines market-specific pricing and content, so a European traveller who leaves the defaults alone gets US-market results. Set all three explicitly from the 49-country, 40-currency and 49-language enums.
Because the hint describes a closed set of partners, not a closed dataset. trivago queries its own contracted advertiser network rather than the open web, so the tool cannot be pointed at an arbitrary source. The contents of that network still change constantly — live rates and availability — which is why idempotentHint is false on the same tools.
Anthropic's directory lists claude, claude-code and claude-desktop, and publishes a claude mcp add command for it. Claude API is not on that list. trivago's own documentation page goes further, giving one-click install buttons for Cursor and VS Code alongside its Claude and ChatGPT instructions, so the vendor targets developer clients directly.
Sources
- Live
initialize,tools/list,prompts/list,resources/list,resources/templates/listandresources/readrequests againsthttps://mcp.trivago.com/mcp(2026-08-18). All returned HTTP 200 anonymously;prompts/listreturned JSON-RPC-32601prompts not supportedinside a 200. Source for the tool count, every schema and annotation claim, the three declared capabilities,serverInfotrivago Accommodation Searchversion0.4.0, the single concrete resource, the 814,170-byte widget document and its dual-namespaced CSP metadata, and the auth posture. Schemas cached atdocs/marketing/data/tool-schemas/trivago.tools.json. · retrieved 2026-08-18 - trivago MCP documentation (retrieved 2026-08-18; HTTP 200). The URL Anthropic's directory publishes as this connector's documentation, served from the MCP host itself. Source for the client setup instructions, the no-API-keys claim, the support address and the
search_hotelsexample that does not match the live server.https://mcp.trivago.com/redirects here and resolves HTTP 200 at this URL. The host publishes norobots.txtand nollms.txt(both 404 on 2026-08-18), so no crawl restriction or machine index applied. · retrieved 2026-08-18 - Anthropic Connectors Directory entry for trivago — , read from the committed snapshot
docs/marketing/data/anthropic-directory-2026-08-16.json. Source for the partner tier, the 2025-11-12 listing date, the endpoint,streamable-http, the productivity category, the two listed tool names, the emptyprompt_namesarray, theno_authposture, theworks_withlist, the Claude Code install string, the documentation and support values and the connector description. The directory URL itself returned HTTP 403 to our client on 2026-08-18, which is why the snapshot is the cited source. · retrieved 2026-08-16 https://www.trivago.com/robots.txt(retrieved 2026-08-18; HTTP 200). A singleUser-agent: *block disallowing specific paths — auth pages, tracking, search-result and map paths, image CDNs and non-platform locales. No named block forClaudeBotorGPTBot, no blanketDisallow: /and noContent-Signalline. We nonetheless fetched no page underwww.trivago.com; every vendor claim on this page comes frommcp.trivago.com/docs. · retrieved 2026-08-18- trivago privacy policy — , the URL published in Anthropic's directory entry. Returned HTTP 403 to our client on 2026-08-18. Listed for reference; not cited for any claim on this page. · retrieved 2026-08-18
- trivago support —
mcp.support@trivago.com, named both by Anthropic's directory and by trivago's own documentation page as the contact point for setup, docs and troubleshooting.
Server Info
- Category
- Productivity
- Developer
- trivago
- Tools
- 2
- Domain
- mcp.trivago.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Productivity
Related Resources
Ready to connect trivago?
Connect trivago once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.