Skip to main content
Glama
README.md
# 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

## Setup

### Prerequisites

Ensure you have the following installed:

- [uv](https://github.com/astral-sh/uv) (used for package management)
- Python 3.13+
- A [Ticketmaster](https://developer.ticketmaster.com/explore/) API key (free to
  use, but rate limited)

### Installation

1. Clone the repository:

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

2. Install dependencies:

    ```sh
    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

```sh
uv run mcp-live-events
```

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

## Resources

- [Introducing the Model Context Protocol](https://www.anthropic.com/news/model-context-protocol)
- [Model Context Protocol Documentation](https://modelcontextprotocol.io/introduction)
- [MCP Server Demo Quickstart](https://modelcontextprotocol.io/quickstart/server)

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.

Maintenance

ActivityInactive
ResponsivenessNo issues