Skip to main content
Glama
Sign In
enesjakozh
MCP Live Events Server

MCP Live Events Server

by mmmaaatttttt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP Live Events Server

mcp-live-events is a Model Context Protocol (MCP) server that integrates with the Ticketmaster API to provide real-time event data. It allows AI agents to fetch concert and event details dynamically.

Features

  • 🎟️ Integrates with the Ticketmaster API to search for events

  • 🗣️ Formats API responses for ease of LLM interpretation

Related MCP server: Eventbrite MCP Server

Setup

Prerequisites

Ensure you have the following installed:

  • uv (used for package management)

  • Python 3.13+

  • A Ticketmaster API key (free to use, but rate limited)

Installation

  1. Clone the repository:

    git clone https://github.com/mmmaaatttttt/mcp-live-events.git
cd mcp-live-events

  2. Install dependencies:

    uv venv
uv sync

  3. Set up your environment variables, i.e. the Ticketmaster API key. This can either be placed in a .env file in this repository, following the pattern of the .env.example file, or it can be placed in an "env" section of this server's configuration in your MCP client.

    Note that on the Ticketmaster developer portal, the API key is named "Consumer Key."

Running the server

uv run mcp-live-events

If it's successful, you should see MCP Live Event server is running! print to your terminal.

Resources

Available Tools

1 tool
get_upcoming_eventsB

Get upcoming music events for a city.

Args: city: City in which to search for events. start_dttm_str: Start date/time in ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ). Example: 2025-02-08T00:00:00Z end_dttm_str: Start date/time in ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ). Example: 2025-02-10T00:00:00Z keyword: Any optional keywords to help filter search results.

Inputs: city (required), start_dttm_str (required), end_dttm_str (required), keyword.

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving upcoming music events for a specified city, making it distinct by default.

    Naming Consistency5/5

    The single tool name 'get_upcoming_events' follows a clear verb_noun pattern (get + upcoming_events), which is consistent within this minimal set. There are no other tools to compare against, so no inconsistency exists.

    Tool Count2/5

    A single tool is too few for a server named 'MCP Live Events Server', which suggests a broader domain of live events management. This minimal toolset feels thin and incomplete for handling events beyond basic retrieval, such as creating, updating, or deleting events.

    Completeness2/5

    The tool surface is severely incomplete for the implied domain of live events. While 'get_upcoming_events' allows retrieval, there are significant gaps: no tools for creating events, updating event details, deleting events, or managing other aspects like tickets or venues, which will likely cause agent failures in comprehensive workflows.

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches