MCP Server for Ticketmaster

Created By
delorenja year ago
A Ticketmaster MCP server that provides query capabilites from the Discovery API
Overview

what is MCP Server for Ticketmaster?

MCP Server for Ticketmaster is a Model Context Protocol server that provides tools for discovering events, venues, and attractions through the Ticketmaster Discovery API.

how to use MCP Server for Ticketmaster?

To use the MCP Server, install it via npm, configure it with your Ticketmaster API key, and utilize the search_ticketmaster tool to query events, venues, or attractions.

key features of MCP Server for Ticketmaster?

  • Flexible search capabilities for events, venues, and attractions with various filters.
  • Outputs data in structured JSON format or human-readable text.
  • Comprehensive data including names, dates, price ranges, and locations.

use cases of MCP Server for Ticketmaster?

  1. Finding concerts and events in a specific city.
  2. Searching for venues based on location and event type.
  3. Discovering attractions and their classifications.

FAQ from MCP Server for Ticketmaster?

  • How do I get a Ticketmaster API key?

You can obtain a Ticketmaster API key by creating an account on the Ticketmaster developer portal and creating a new app.

  • What types of searches can I perform?

You can search for events, venues, and attractions using various filters like keyword, date range, and location.

  • Is there a limit to the number of queries?

The API may have rate limits; please refer to the Ticketmaster API documentation for details.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
delorenj
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago