io.github.chrischallPublished by GitHub account chrischallv1.2.0Updated Nov 5, 2026
TripAdvisor location search, details, photos, and reviews via the Terra API
TripAdvisor travel data for an assistant: search hotels, restaurants and attractions, then pull details, photos and reviews via the Terra API.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
MCP server for the TripAdvisor Terra API — travel data for Claude. Search hotels, restaurants, and attractions by name or coordinates, then pull full details, photos, and reviews, all over stdio. (Terra is TripAdvisor's current API; the legacy Content API is sunset on 2026-08-31.)
Developed and maintained by AI (Claude Code). Use at your own discretion.
Get a key at tripadvisor.com/developers. The free Discover tier is pay-as-you-go (10 QPS, 10,000 calls/day); responses are cached in-memory to stretch it. Make sure it's a Terra key — a legacy Content API key returns 403.
All tools are read-only — Terra has no write endpoints.
ta_web_healthcheck is the first tool of an optional second tier that reaches
tripadvisor.com's consumer site (bot-walled, so unreachable server-side) by
routing same-origin fetches through your signed-in browser tab via the
ContextMint Bridge browser extension, installed from
its releases page
(Chrome: download the chrome zip and load it unpacked from chrome://extensions
with Developer mode on; Safari isn't available yet — it will ship inside the
ContextMint app, which has no public download — so use Chrome for now). It needs
the extension installed and a one-time pairing approval; the Content API tools
above never touch the bridge.
ContextMint Bridge is the fetchproxy browser extension under its new name, from
the same maintainer — fetchproxy's own README
(https://github.com/chrischall/fetchproxy#extension) points to it. Its source is
public at https://github.com/nullnet-app/contextmint-bridge: build it yourself,
or check a release zip against the .sha256 file published beside it
(shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).
ta_web_get_location uses this bridge to read a location's details straight
from its public TripAdvisor page — so it works without an API key,
covering attractions, hotels, and restaurants. It returns core business data
(rating, review count, address, coordinates, phone, primary photo, listing
URL) but not individual review text. Request shapes are pinned in
docs/TRIPADVISOR-WEB-API.md.
Endpoint request shapes are pinned in docs/TRIPADVISOR-API.md. With a key in .env, node scripts/live-probe.mjs exercises every read path through the built client.
MIT
Source: README.md at commit 597b2a5
Search TripAdvisor locations (restaurants, attractions, hotels) by name. Returns matches with a location id for the detail tools, plus pagination. Returns slim summaries by default; pass view:"full" for the whole records.
pagesizeviewqueryrequiredlocalecategorygeo_namepostal_codecountry_codeFind TripAdvisor locations near a point within a radius, or inside a bounding box. Center by lat+lon+radius, by a reference location_id+radius, or by a sw/ne bounding box. Returns matches with distance and a location id. Returns slim summaries by default; pass view:"full" for the whole records.
latlonpagesizesortunitviewlocalene_latne_lonradiussw_lat+5 moreGet details for MULTIPLE locations in one call (batch). Pass an array of location ids — cheaper than repeated ta_get_location_details. Unknown or unlicensed ids are silently omitted. Returns slim summaries by default; pass view:"full" for the whole records.
idsrequiredviewlocaleGet full details for a TripAdvisor location: names, descriptions, address, coordinates, traveler ratings, phone, category, and listing URLs. Rating-icon and other incidental image URLs are dropped by default; pass view:"full" for TripAdvisor's whole record.
viewlocalelocationIdrequiredGet photos for a TripAdvisor location (multi-size image URLs, source, dimensions), with pagination.
pagesizelocalelocationIdrequiredGet traveler reviews for a TripAdvisor location, with pagination. Reviewer avatars and other image URLs are dropped by default; pass view:"full" for TripAdvisor's whole records.
pagesizeviewlocalelocationIdrequiredVerify the ContextMint Bridge connection end-to-end
Round-trips a small public www.tripadvisor.com URL (/) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.tripadvisor.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke.
Takes no parameters.
Get a TripAdvisor location's core details (name, rating, review count, address, coordinates, phone, photo, listing URL) by location ID, read from the public page via the browser bridge. Works without an API key — use this when ta_get_location_details is unavailable or its key is blocked. Covers attractions, hotels, and restaurants. Does not return individual review text.
locationIdrequired90% 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.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
{ "mcpServers": { "tripadvisor": { "command": "npx", "args": ["-y", "@chrischall/tripadvisor-mcp"], "env": { "TRIPADVISOR_API_KEY": "your-terra-api-key-here" } } }}npm installnpm run build # tsc + esbuild bundlenpm test # vitest (no real network)