How do I install Etix?

Etix is a local plugin. Install it using npm package: etix-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Etix need?

Etix requires the following credentials or environment variables: ETIX_WS_PORT. You can find setup instructions on the server detail page.

What AI apps work with Etix?

Etix uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Etix MCP Server

by Chris Hall

Developer ToolsModerate6.6LocalNew

Free

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

About

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

Security Report

6.6

Moderate6.6Moderate Risk

etix-mcp is a well-structured event discovery MCP server with solid security practices. Authentication is handled via the user's existing signed-in browser session (proxied through fetchproxy), which is appropriate for its design. Code quality is good with proper error handling, input validation through schema parsing, and no evident malicious patterns. Permissions are appropriately scoped to network HTTP calls and environment variable access, matching the server's stated purpose of querying Etix's consumer API. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

7 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Override the fetchproxy WebSocket port (default 37149).Optional

Environment variable: ETIX_WS_PORT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-etix-mcp": {
      "env": {
        "ETIX_WS_PORT": "your-etix-ws-port-here"
      },
      "args": [
        "-y",
        "etix-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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 fetchproxy 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 SKILL.md for full install steps: add the server to your MCP config, install the shared fetchproxy extension, open etix.com, and approve the one-time pairing. Then run etix_healthcheck.

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