Dice MCP server

@pipeworx/dice

Live event, venue and lineup listings from DICE (dice.fm) — city-by-city browse of on-sale gigs, DJ sets, parties, comedy, theatre and talks, plus full detail (dates, venue, starting price, billed artists) for any one event.

Part of Pipeworx — an MCP gateway connecting AI agents to 1800+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

worldwide, optionally filtered by a name/country substring. Each city's id + permname is what dicebrowse needs.

• dice_cities(query?) — the full list of cities DICE sells tickets in

optionally filtered by category (e.g. "DJ", "Comedy", "Theatre"). Returns name, status, dates, venue and starting price for each event.

• dice_browse(city, category?) — events currently on sale in one city,

address, dates, on-sale window, starting price, billed lineup, and highlights (age restriction, promoter). Needs the id from dice_browse.

• diceevent(eventid) — full detail for one event: description, venue +

Auth

Keyless. api.dice.fm answers 403 without a key and is never called; this pack reads the same server-rendered pages any anonymous visitor's browser loads.

Data sources

as served to any anonymous visitor. No attendee/guest list or buyer contact data is exposed by any tool here; only public event, venue and billed-artist information.

• DICE (dice.fm) — the platform's own public event, venue and city listings,

Notes

(typically 20-30 events). page=/nextCursor on the browse page were both probed live and neither advances past the first batch — deeper paging goes through api.dice.fm, which this pack cannot reach keylessly. Results are not artificially truncated below what the page itself returns.

• dice_browse's result set is whatever DICE's own server-rendered page ships

field. The bare-id event URL 308-redirects to the canonical slugged URL; a plain fetch() follows it, so the bare id is all callers need.

• diceevent takes the bare event id (24-char hex) from dicebrowse's id

full permname-id browse slug (e.g. "newyork-5bbf4db0f06331478e9b2c59"), matched case-insensitively against the live city directory (not a hardcoded list) — so DICE adding or renaming a city needs no code change here.

• City resolution in dicebrowse accepts a city name, permname, or the

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "dice": {
      "url": "https://gateway.pipeworx.io/dice/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/dice/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Shortened. The full README is on GitHub.