6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search accommodation on trivago from an AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The trivago MCP server gives Claude, ChatGPT and any MCP client two read-only hotel searches over trivago's metasearch: one that takes a destination name, one that takes coordinates. No sign-in. Results carry provider names, prices, ratings and links, and render on an interactive map widget. Nothing books — the connector compares and hands you a link.
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.
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.
idempotentHint: false on 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.search_hotels with destination, check_in, check_out and guests. No such tool exists on the server; take names and parameters from tools/list.country defaults to US, currency to USD and language to EN_US. The schema says country changes pricing and content, not just display.arrival and departure are typed as plain strings with no format or pattern. The rules that arrival be future-dated and precede departure are instructions in the descriptions, addressed to the model.rooms constraint is also prose-only. The schema says rooms must not exceed the number of adults; no structural constraint enforces it.prompts/list returns -32601 prompts not supported.mcp-app widget. A client that does not implement the extension gets the structured tool output without the map.429. We make no claim about one.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_with omits Claude API. The directory lists Claude, Claude Code and Claude Desktop only.initialize, tools/list, prompts/list, resources/list, resources/templates/list and one resources/read. Every behavioural claim above comes from the schemas, the resource, the directory or trivago's documentation page.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.
initialize, tools/list, prompts/list, resources/list, resources/templates/list and resources/read requests against https://mcp.trivago.com/mcp (2026-08-18). All returned HTTP 200 anonymously; prompts/list returned JSON-RPC -32601 prompts not supported inside a 200. Source for the tool count, every schema and annotation claim, the three declared capabilities, serverInfo trivago Accommodation Search version 0.4.0, the single concrete resource, the 814,170-byte widget document and its dual-namespaced CSP metadata, and the auth posture. Schemas cached at docs/marketing/data/tool-schemas/trivago.tools.json. · retrieved 2026-08-18search_hotels example that does not match the live server. https://mcp.trivago.com/ redirects here and resolves HTTP 200 at this URL. The host publishes no robots.txt and no llms.txt (both 404 on 2026-08-18), so no crawl restriction or machine index applied. · retrieved 2026-08-18docs/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 empty prompt_names array, the no_auth posture, the works_with list, 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-16https://www.trivago.com/robots.txt (retrieved 2026-08-18; HTTP 200). A single User-agent: * block disallowing specific paths — auth pages, tracking, search-result and map paths, image CDNs and non-platform locales. No named block for ClaudeBot or GPTBot, no blanket Disallow: / and no Content-Signal line. We nonetheless fetched no page under www.trivago.com; every vendor claim on this page comes from mcp.trivago.com/docs. · retrieved 2026-08-18mcp.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.Connect trivago once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.