Technical reference

JamBase Data MCP

Plug 25+ years of normalized live music data into ChatGPT, Claude, Cursor, Gemini CLI, or Replit. Built on the Model Context Protocol — OAuth handles auth on first connect, no API key to paste.

For the marketing pitch and per-client install snippets, see /mcp. If you’re signed in, your one-click install page lives at /account/mcp.

What you’ll be able to do

Three sample conversations a JamBase-connected assistant can handle that nothing else on the market can.

“Who's playing Red Rocks this August?”

Your assistant returns the full month of dates, headliners, and confirmed openers, pulled live from the JamBase calendar.

“Which of my saved artists are touring near me in the next 90 days?”

Your assistant joins your personal artist list against the global tour calendar and ranks the answer by distance and date.

“Pair a jam-band show near Sonoma with three wineries I should pitch.”

Your assistant uses JamBase to find the right show and date, then layers in winery research from its other tools — a join nobody else's data lets you make.

If you’re a PM or analyst evaluating whether to wire this in, the marketing pitch and per-assistant install snippets live at /mcp. The rest of this page covers the technical reality.

What is MCP?

The Model Context Protocol is the open standard MCP-aware assistants use to call external tools.

When you connect JamBase Data to your assistant, it shows up as a set of callable tools (e.g. searchEvents). The assistant decides when to call them, supplies the arguments, and folds the results into its answer. You don't write any glue code — just connect the server once and start asking music questions.

Server URL

Point any MCP-compatible client at this URL.

MCP server endpoint

https://mcp.jambase.com/mcp

Connect your assistant

Per-client install snippets and step-by-step setup live on the marketing page so the same instructions work whether you’re logged in or not.

For ChatGPT and Claude, the recommended install is one click from the directories: JamBase is live in the ChatGPT Apps directory and the Claude connectors directory. Any other MCP-compatible client can point at the server URL above.

We maintain copy-paste install snippets for ChatGPT, Claude Desktop, Cursor, Gemini CLI, and Replit at /mcp. If you're already signed in, your account-page version with your own server URL pre-filled lives at /account/install-in-your-ai.

  1. Copy the snippet for your assistant from the install grid.
  2. Paste it into the assistant's MCP / connectors settings.
  3. Restart the assistant.
  4. The first time the assistant calls a JamBase tool, it pops a browser window for OAuth sign-in. Approve once and the access token is stored for you.

Your first prompt

Paste any of these into your connected assistant — no further setup needed.

"Who is playing at Red Rocks this August?"

The assistant will call searchEvents with the venue name and an August date range, then format the results back to you with dates, artists, and confirmed openers.

More starter prompts (artists, livestreams, festivals, geo lookups) live on the marketing page under "Try these queries".

Available tools

The MCP server currently exposes these tools. The assistant picks which one to call based on your prompt.

Search & discovery

searchEvents
Find concerts and festivals by venue, city, metro, artist, date range, genre, or event title (pass a festival or tour name as the name argument — matching is on the title only, not the lineup or description).
searchArtists
Look up artists by name, including upcoming dates and cross-references to Spotify and MusicBrainz.
searchVenues
Find venues by name or location with capacity, address, and upcoming shows.
searchFestivals
Find upcoming festivals by name, location, or date range.
searchFestivalCollections
Find recurring festival series (e.g. a festival across all its editions).
searchStreams
Find upcoming and recent livestreams by artist or date.
findArtistAndFetchEvents
Resolve an artist by name and return their upcoming events in one call.
findVenueAndFetchEvents
Resolve a venue by name and return its upcoming events in one call.

Entity lookups

getEvent
Fetch a single event by JamBase ID with full details.
getArtist
Fetch a single artist by JamBase ID.
getVenue
Fetch a single venue by JamBase ID.
getStream
Fetch a single livestream by JamBase ID.
getFestivalSeriesArchive
Fetch the edition-by-edition archive of a festival series.

Geo & vocabulary

searchCities
Resolve city names to JamBase geo IDs for use in event filters.
getCity
Fetch a single city by JamBase geo ID.
getMetro
Fetch a single metropolitan area by JamBase geo ID.
getMetros
Resolve metropolitan area names to JamBase geo IDs.
getGenres
Enumerate the canonical JamBase genre vocabulary for filtering events and artists.

Personalization (beta)

Opt-in, available to every signed-in user who connects a jambase.com fan account at /account/fan-link. Users who haven't connected get a short in-chat message with a link to set it up.

getMyFollowedArtistsUpcomingShows
Upcoming shows for the artists you follow on your linked jambase.com fan account.
getMyLocalShows
Upcoming shows in the home city on your linked fan profile.
getMyRecommendedShows
Upcoming shows from artists recommended by co-follow overlap with fans who share your taste.
getMyArticleFeed
JamBase News articles about the artists you follow.

News & feedback

searchArticles
Search JamBase News articles by free-text query, tag, or publish-date window.
getArticlesForArtist
Recent JamBase News coverage of a specific artist.
getArticlesForEvent
JamBase News coverage related to a specific event's performers.
submitToolFeedback
Send feedback about a tool response straight to the JamBase Data team.

Title search is fail-soft: if the search backend is unavailable, an event-title query returns zero hits (an empty result), never an error.

Authentication

OAuth 2.1 with Dynamic Client Registration is the default; long-lived API keys are available for non-MCP clients.

MCP-compatible assistants use OAuth 2.1 + Dynamic Client Registration. The first tool call opens a JamBase sign-in window in your browser; the assistant stores the resulting access token and refreshes it automatically.

For non-MCP clients (CLIs, scripts, server-side jobs) a long-lived JBD API key (jbd_*) works against the same data via the REST API. See Authentication for details.

When to use the REST API instead

MCP shines for interactive answers. Bulk pulls and background jobs belong on REST.

If you're running nightly ingests, populating an analytics warehouse, or building an ID-mapping pipeline, the REST API at api.data.jambase.com/v3 hits the same data with the same JBD API key. Start with the REST quickstart.

Wiring the REST API in with a coding agent (Cursor, Claude Code, Windsurf, Replit Agent)? The build-time Agentic Developer Guide ships an agents.md the agent reads to scaffold env, auth, the paginated bulk seed, and the dateModifiedFrom delta loop on the first run.

Last updated Aug 1, 2026