Etix Mcp

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

Etix event discovery for Claude — search events, venues & performers and fetch event details

概览

AI 生成的概览

通过用户自己已登录的浏览器标签页搜索 Etix 的活动、场馆和演出者,并获取活动、场馆与地点详情。

可以做什么
  • 按关键词搜索 Etix 的活动、场馆和演出者,返回各自的 id 与规范链接
  • 按 id 获取单个活动:名称、日期时间、场馆地址与坐标、主办方、票价区间及各档报价
  • 按 id 获取单个场馆:主办方、完整地址及该场馆的近期活动与购票链接
  • 将城市名或邮政编码解析为坐标及规范化的城市/州
  • 运行桥接健康检查,往返访问一个公开页面并报告哪一环失败
适用场景
适合希望用自然语言查询 Etix 演出、场馆和票价区间,或基于位置浏览活动的场景,且无需 Etix 账号。
运行要求
以 npm 包形式通过 stdio 在本机运行。需要安装 ContextMint Bridge 浏览器扩展、打开已登录的 etix.com 标签页并完成一次性配对;请求经本地 WebSocket 桥接(默认端口 37149)。可选环境变量:ETIX_DEBUG、ETIX_WS_PORT、FETCHPROXY_IDENTITY_DIR、FETCHPROXY_WS_HOST。
安装前请注意
Etix 未公开消费者 API,且站点设有机器人防护;该服务器通过你的浏览器会话读取相同的接口和页面,以你的 Cookie 和 JS 环境行事,使用需自行斟酌,可能与站点条款冲突。必须安装并配对桥接扩展,其身份密钥对存放于 FETCHPROXY_IDENTITY_DIR。FETCHPROXY_WS_HOST 应保持在本机回环地址。所有工具均为只读。

安装

在 SourceWeft 中

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

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

其他 MCP 客户端

参照 仓库 中的启动说明。

README

etix-mcp

Etix event discovery as an MCP server for Claude — search events, venues, and performers and pull full event/venue details via natural language.

⚠️ Etix does not publish a public consumer API, and its consumer site sits behind a DataDome bot-wall. This server reads the same /ticket/api/online/... endpoints and server-rendered pages that etix.com itself uses, routed through your own signed-in browser tab via the ContextMint Bridge browser extension. Every request acts on behalf of your existing session — your cookies, your TLS, your JS context — exactly as if you'd browsed it yourself. No Etix account is required; this is public discovery data. Use at your own discretion.

Tools

ToolPurpose
etix_searchSearch events, venues, and performers by keyword. Returns a few top matches per category, each with its id and canonical etix.com URL.
etix_get_eventFull record for an event/performance by event_id — name, date/time, venue (with address + coordinates), organizer, ticket price range and the individual priced offer levels.
etix_get_venueA venue by venue_id — name, organizer, full address, and the list of upcoming events at that venue.
etix_find_locationResolve a city name or postal code to coordinates plus normalized city/state — a building block for location-based event browsing.
etix_healthcheckEnd-to-end bridge check — round-trips /robots.txt and reports which hop failed (bridge down vs. extension not connected vs. DataDome challenge on your tab). Call when other tools fail.

How it works

Etix fronts its consumer site with a DataDome interstitial that a server-side fetch can't clear, so etix-mcp routes every request through your signed-in, already-cleared etix.com tab via the shared fetchproxy bridge (WebSocket on 127.0.0.1:37149). etix_search reads the clean search/suggest JSON endpoint; etix_get_event and etix_get_venue parse the server-rendered performance/venue pages (schema.org JSON-LD + microdata). See docs/ETIX-API.md for the verified endpoint shapes.

Setup

See skills/etix/SKILL.md for full install steps: add the server to your MCP config, install the shared ContextMint Bridge extension, open etix.com, and approve the one-time pairing. Then run etix_healthcheck.

Where the extension comes from. ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (chrischall/fetchproxy#extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself (npm run build), or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).

Development

bash
npm cinpm run build   # tsc --noEmit + esbuild bundle → dist/bundle.jsnpm test        # vitest

Acknowledgement of Terms

By using this MCP server, you acknowledge that it uses your own etix.com session via the ContextMint Bridge extension, that Etix offers no public consumer API (so the underlying endpoints may change at any time), and that this is an unofficial, AI-developed project with no affiliation to Etix. Use at your own discretion, consistent with Etix's Terms of Use.

License

MIT — developed and maintained by AI (Claude Code).

来源:README.md,提交 a53a2ec

工具

5

etix_get_event

Get an Etix event/performance by id

Fetch a single Etix event (performance) by its numeric event_id — name, date/time, venue (with address + coordinates), organizer, ticket price range and the individual priced offer levels. Get the event_id from etix_search. Read-only, no Etix account required.

输入参数event_id必填

etix_get_venue

Get an Etix venue and its upcoming events by id

Fetch a single Etix venue by its numeric venue_id — name, organizer, full address, and the list of upcoming events at that venue (each with event_id, name, start time, and ticket URL). Get the venue_id from etix_search. Follow up with etix_get_event for any listed event. Read-only, no Etix account required.

输入参数venue_id必填

etix_find_location

Resolve a city or postal code to coordinates

Resolve a city name or postal code to coordinates (latitude/longitude) plus the normalized city/state, using Etix's geolocation lookup. Useful as a building block for location-based event browsing. Returns found:false with a message when nothing matches. Read-only, no Etix account required.

输入参数query必填country

etix_healthcheck

Verify the ContextMint Bridge connection end-to-end

Round-trips a small public www.etix.com URL (/robots.txt) 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.etix.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke.

无需输入参数。

版本历史

13
  1. v1.2.0最新Nov 4, 2026
  2. v1.1.9Oct 29, 2026
  3. v1.1.8Oct 16, 2026
  4. v1.1.7Oct 10, 2026
  5. v1.1.6Oct 7, 2026
  6. v1.1.5Oct 5, 2026
  7. v1.1.4Oct 3, 2026
  8. v1.1.3Sep 28, 2026
  9. v1.1.2Sep 23, 2026
  10. v1.1.1Sep 23, 2026
  11. v1.1.0Sep 20, 2026
  12. v1.0.0Sep 18, 2026
  13. v0.6.4Sep 16, 2026

评分

已满足适用检查项的 80%

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

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

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

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

    请在仓库或注册中心条目中声明许可证。