Skip to main content
Glama

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

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.

Related MCP server: Ticketmaster Discovery MCP Server

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

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

Available Tools

5 tools
etix_find_locationResolve a city or postal code to coordinatesA
Read-onlyIdempotent

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.

Inputs: query (required), country.

etix_get_eventGet an Etix event/performance by idA
Read-onlyIdempotent

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.

Inputs: event_id (required).

etix_get_venueGet an Etix venue and its upcoming events by idA
Read-onlyIdempotent

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.

Inputs: venue_id (required).

etix_healthcheckVerify the ContextMint Bridge connection end-to-endA
Read-onlyIdempotent

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.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The four Etix domain tools are largely distinct: search is a discovery entry point, get_event and get_venue are ID-based detail lookups, and healthcheck is an explicit diagnostic utility. The main wrinkle is etix_find_location, which returns coordinates but has no consuming tool, leaving its role somewhat orphaned.

    Naming Consistency4/5

    All tools share the etix_ prefix and are mostly verb_noun (find_location, get_event, get_venue), which is predictable. Minor deviations are etix_search (bare verb) and etix_healthcheck (noun, no verb_noun form).

    Tool Count4/5

    Five read-only lookup/diagnostic tools is a compact, well-scoped set with no obvious redundancy. It is a touch thin for an event-browsing surface, but each tool earns its place.

    Completeness3/5

    The read-only discovery surface covers search, event detail, venue detail, and connectivity diagnostics, but find_location produces coordinates that no other tool accepts, and there is no way to browse events by city, date, or category. These are notable gaps for location-based event browsing, which the description explicitly advertises.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Related MCP Connectors

    • Eventbrite MCP server for ChatGPT, Claude and any AI agent: list events, list orders, list attendees, check in attendees, email attendees, refund order, create promo code and search public events in your own Eventbrite account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Eventbrite yourself; Cotlet does not store your password and you need no Eventbrite API key. About the official Eventbrite API: Eventbrite has a full public REST API (v3) for events, orders, attendees, discounts and reports, but no Eventbrite-hosted MCP server and no public event search (checked 5 Nov 2026). Its Event Search API was shut down on 12 Dec 2019. Setup and FAQ: https://cotlet.dev/integrations/eventbrite-api-mcp-server

    • Tiqets MCP server for ChatGPT, Claude and any AI agent: search tickets, check availability, book tickets, list my bookings, download e-tickets and cancel booking in your own Tiqets account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Tiqets yourself; Cotlet does not store your password and you need no Tiqets API key. About the official Tiqets API: Tiqets has an API only for distribution partners such as travel agencies, not for customers (checked 11 Oct 2026). It lists the orders a partner generated, so it cannot see the bookings or tickets of your own Tiqets account. Setup and FAQ: https://cotlet.dev/integrations/tiqets-api-mcp-server

      https://cotlet.dev/mcp/v1/tiqets
    • Bandsintown MCP server for ChatGPT, Claude and any AI agent: add event, update event, delete event, send fan message, get fan stats and list upcoming events in your own Bandsintown account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Bandsintown yourself; Cotlet does not store your password and you need no Bandsintown API key. About the official Bandsintown API: Bandsintown has a public API, but it only reads: artist info and artist events (checked 11 Oct 2026). You cannot add, edit or delete events, post to followers or read Insights through it, and each API key is tied to one artist. Setup and FAQ: https://cotlet.dev/integrations/bandsintown-api-mcp-server

    • DICE MCP server for ChatGPT, Claude and any AI agent: create event, update ticket tier, get sales report, list ticket holders and issue comp tickets in your own DICE account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to DICE yourself; Cotlet does not store your password and you need no DICE API key. About the official DICE API: DICE has a read-only partner API, the Ticket Holders GraphQL API, with a token you generate in MIO (checked 11 Oct 2026). It reads events, tickets, orders, returns and transfers, and documents no mutations, so it cannot create events, change ticket types or message fans. Setup and FAQ: https://cotlet.dev/integrations/dice-api-mcp-server

      https://cotlet.dev/mcp/v1/dice

    Related MCP Servers