About etix-mcp
etix-mcp is an event-discovery MCP server for Claude that searches Etix events, venues, and performers and retrieves detailed records. It accesses Etix page data through the user's signed-in browser tab.
Key features
- 01Search events, venues, and performers
- 02Retrieve event and performance details
- 03View venue addresses and upcoming events
- 04Resolve cities or postal codes to coordinates
- 05Check browser bridge status
Use cases
- 01Find events by keyword
- 02Review performance times and ticket price ranges
- 03Browse upcoming events at a venue
- 04Use a city location for event browsing
MCP support
The MCP server provides Claude with Etix search, detail lookup, location resolution, and health-check tools. Requests are routed through ContextMint Bridge using the user's signed-in Etix browser tab.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y etix-mcpETIX_WS_PORTOverride the fetchproxy WebSocket port (default 37149).ETIX_DEBUGSet to 1 for stderr per-request bridge timing.FETCHPROXY_WS_HOSTBind interface for the bridge (default 127.0.0.1; a literal IP only, anything else is ignored). Keep on loopback — it exists for ONE topology: a hosted child in its own network namespace.FETCHPROXY_IDENTITY_DIRWhere to store the long-term fetchproxy identity keypair (default ~/.fetchproxy/identity/; an absolute path only, anything else is ignored). Exists for a host that runs a separate child per caller, so they can share one identity.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| keywords | string | Yes | Search text — an artist, event, or venue name (e.g. "jazz", "Marion Meadows"). |
Details
From the project READMEetix-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
| Tool | Purpose |
|---|---|
etix_search | Search events, venues, and performers by keyword. Returns a few top matches per category, each with its id and canonical etix.com URL. |
etix_get_event | Full 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_venue | A venue by venue_id — name, organizer, full address, and the list of upcoming events at that venue. |
etix_find_location | Resolve a city name or postal code to coordinates plus normalized city/state — a building block for location-based event browsing. |
etix_healthcheck | End-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.sha256file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).
Development
npm ci
npm run build # tsc --noEmit + esbuild bundle → dist/bundle.js
npm 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).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.