- Home
- MCP servers
- Ticketmaster Partner
Ticketmaster Partner
- javascript
0
GitHub Stars
javascript
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"robandrewford-mcp-server-tm-partner": {
"command": "npx",
"args": [
"-y",
"@delorenj/mcp-server-tm-partner"
],
"env": {
"TM_PARTNER_API_KEY": "YOUR_PARTNER_API_KEY",
"TM_PARTNER_API_SECRET": "YOUR_PARTNER_API_SECRET"
}
}
}
}You can run a dedicated MCP server that interfaces with the Ticketmaster Partner API to discover events, venues, and attractions with flexible filtering and output options. This server exposes a simple toolset you can call from your MCP client to perform targeted searches, facilitating rich data for applications, dashboards, or integrations.
How to use
You use the Ticketmaster Partner MCP server by starting it as an MCP service and then invoking its search tool from your MCP client. The server exposes a single core tool that lets you search for events, venues, or attractions with a variety of filters and output formats. Practical usage patterns include:
-
Search events with date windows, on-sale dates, locations, and classifications to surface concerts, sports, and other live experiences.
-
Find venues near a geographic location by latitude/longitude or within a radius, then refine by market or city.
-
Filter attractions by classification and keyword to discover relevant partner content.
To run a search, you provide the search type (event, venue, or attraction), optional filters, and your preferred output format. The server handles querying the Partner API and returns structured JSON by default or human-friendly text when requested.
How to install
Prerequisites you need before starting the server:
-
Node.js and npm installed on your machine.
-
Access to Ticketmaster Partner API credentials (API key and secret) to configure the server securely.
Install the MCP server using one of the following methods.
# Option 1: Install globally with npm
npm install -g @delorenj/mcp-server-tm-partner
# Option 2: Install via Smithery (for Claude Desktop or compatible clients)
npx -y @smithery/cli install @delorenj/mcp-server-tm-partner --client claude
Configuration and running
Create an MCP settings configuration that includes the server entry for the TM Partner MCP. The configuration uses a stdio (local) server command since it runs locally via a package runner. Include your Partner API credentials in the environment.
{
"mcpServers": {
"tm-partner": {
"command": "npx",
"args": ["-y", "@delorenj/mcp-server-tm-partner"],
"env": {
"TM_PARTNER_API_KEY": "YOUR_PARTNER_API_KEY",
"TM_PARTNER_API_SECRET": "YOUR_PARTNER_API_SECRET"
}
}
}
}
Using the server tool
After starting the MCP server, use the search_tm_partner tool from your MCP client. You specify the type of search (event, venue, or attraction) and optional parameters such as keyword, date ranges, location, radius, and classifications. You can request results in JSON for programmatic use or in a human-readable text format for quick inspection.
Notes on output and paging
The server supports pagination with up to 200 results per page. If you need more results, request subsequent pages by adjusting the page parameter. Output formats include json for machine consumption and text for human reading.
Security and credentials
Keep your Partner API credentials secure. Do not commit API keys or secrets to version control. Use environment variables in your MCP settings and restrict access to the server as needed.
Troubleshooting
If you encounter authentication errors, double-check that TM_PARTNER_API_KEY and TM_PARTNER_API_SECRET are correctly set in the MCP configuration. Verify that you are using valid Partner API credentials with appropriate access. Check that the server process is running and that your MCP client is configured to reach the local/remote MCP endpoint.
API differences and capabilities
The Partner API provides more detailed data and higher rate limits for production use, along with access to partner-specific features and endpoints. This MCP server exposes those capabilities through its search tool, enabling richer discovery and filtering compared to standard public APIs.
Development and tools
Key tool provided: search_tm_partner. It enables querying events, venues, and attractions with filters like keyword, date/time ranges, location, radius, classifications, and market options. It outputs structured data suitable for downstream processing.
Available tools
search_tm_partner
Tool to query the Ticketmaster Partner API for events, venues, and attractions with filtering options and configurable output formats.