Tripadvisor Mcp

io.github.chrischall由 GitHub 账号 chrischall 发布v1.2.0更新于 Nov 5, 2026

TripAdvisor location search, details, photos, and reviews via the Terra API

概览

AI 生成的概览

为助手提供 TripAdvisor 旅行数据:通过 Terra API 搜索酒店、餐厅和景点,并获取详情、照片和评论。

可以做什么
  • 按名称搜索地点,可按类别、国家或邮编限定范围
  • 按经纬度、参考地点或边界框查找附近地点
  • 获取单个地点的完整详情,或一次批量查询多个地点 ID
  • 分页获取照片和旅客评论
  • 诊断可选的浏览器桥接,并在无 API 密钥时读取地点公开页面
适用场景
适合让助手做旅行调研、比较酒店、餐厅或景点,或在规划行程时获取评分、地址和评论。所有工具均为只读,适合查询而非预订或修改数据。
运行要求
通过 npx 以 stdio 在本地运行(需要 Node.js)。Terra 工具需要 TripAdvisor Terra API 密钥,放在 TRIPADVISOR_API_KEY 中,以 X-API-Key 请求头发送;旧版 Content API 密钥会返回 403。ta_web_* 工具无需密钥,但需要在 Chrome 中安装 ContextMint Bridge 浏览器扩展并完成一次性配对授权。另有可选的缓存、超时和调试变量。
安装前请注意
Terra 的 Discover 套餐按用量计费并有每日调用配额,使用可能产生费用;默认开启缓存以节省额度。浏览器桥接会通过你已登录的浏览器标签页转发请求,需要配对授权;README 说明该项目由 AI 开发,需自行斟酌使用。所有工具均为只读。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Tripadvisor Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

tripadvisor-mcp

[npm]

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.

Quick start

json
{  "mcpServers": {    "tripadvisor": {      "command": "npx",      "args": ["-y", "@chrischall/tripadvisor-mcp"],      "env": { "TRIPADVISOR_API_KEY": "your-terra-api-key-here" }    }  }}

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.

Tools

ToolWhat it does
ta_search_locationsSearch locations by name (optionally scoped by category, country/geo/postal code) — paginated; compact:true for slim summaries
ta_search_nearbyFind locations near a lat/lon+radius, a location_id+radius, or inside a sw/ne bounding box (category, min rating, sort) — compact:true supported
ta_get_location_detailsFull details: names, descriptions, address, coordinates, traveler ratings, phone, listing URLs
ta_get_locationsBatch — details for multiple location ids in one call (cheaper than N detail calls); compact:true supported
ta_get_location_photosPhotos with multi-size image URLs, source, and dimensions — paginated
ta_get_location_reviewsTraveler reviews — paginated
ta_web_healthcheckDiagnose the optional tripadvisor.com browser-bridge connection (see below)
ta_web_get_locationLocation details (rating, address, coords, phone, photo) read from the public page via the browser bridge — no API key needed

All tools are read-only — Terra has no write endpoints.

Browser bridge (optional)

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.

Environment

VarRequiredPurpose
TRIPADVISOR_API_KEYfor the Terra toolsTerra API key, sent as the X-API-Key header. The ta_web_* tools work without it.
TRIPADVISOR_CACHE_TTLnoSeconds to cache search responses (default: 300; 0 disables).
TRIPADVISOR_STATIC_CACHE_TTLnoSeconds to cache details/photos/reviews (default: 3600; 0 disables).
TRIPADVISOR_REQUEST_TIMEOUT_MSnoPer-request timeout for the optional browser bridge (default: 30000).
TRIPADVISOR_DEBUG_LOGnoSet to 1 to log browser-bridge requests to stderr.

Development

bash
npm installnpm run build   # tsc + esbuild bundlenpm test        # vitest (no real network)

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.

License

MIT

来源:README.md,提交 597b2a5

工具

8

ta_search_locations

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.

输入参数pagesizeviewquery必填localecategorygeo_namepostal_codecountry_code

ta_search_nearby

Find 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 个

ta_get_locations

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

输入参数ids必填viewlocale

ta_get_location_details

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

输入参数viewlocalelocationId必填

ta_get_location_photos

Get photos for a TripAdvisor location (multi-size image URLs, source, dimensions), with pagination.

输入参数pagesizelocalelocationId必填

ta_get_location_reviews

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

输入参数pagesizeviewlocalelocationId必填

ta_web_healthcheck

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

无需输入参数。

ta_web_get_location

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.

输入参数locationId必填

版本历史

16
  1. v1.2.0最新Nov 4, 2026
  2. v1.1.13Oct 29, 2026
  3. v1.1.12Oct 17, 2026
  4. v1.1.11Oct 17, 2026
  5. v1.1.10Oct 16, 2026
  6. v1.1.9Oct 10, 2026
  7. v1.1.8Oct 10, 2026
  8. v1.1.7Oct 7, 2026
  9. v1.1.6Oct 5, 2026
  10. v1.1.5Oct 3, 2026
  11. v1.1.4Sep 28, 2026
  12. v1.1.3Sep 25, 2026
  13. v1.1.2Sep 23, 2026
  14. v1.1.0Sep 20, 2026
  15. v1.0.0Sep 19, 2026
  16. v0.6.4Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分