Resident Advisor MCP server

@pipeworx/resident-advisor

Resident Advisor (RA) electronic music event listings — look up areas/cities, browse club nights and festivals by date range and genre, and pull up artist/DJ and venue/club profiles with their recent and upcoming listed events.

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

Tools

city/region/country name (e.g. "London"); also returns event and venue counts for that area.

• rasearchareas(query, limit?) — look up RA's numeric area id for a

— list events in an area over a date range, optionally filtered by genre (e.g. "techno", "house", "disco").

• raeventlistings(areaid, datefrom, dateto?, genre?, page?, pagesize?)

genres, promoters.

• raevent(eventid) — full event detail: times, cost, venue, lineup,

count, country, social links) and recent/upcoming listed events; resolves a free-text name via RA's own search if no id is given.

• raartist(name?, artistid?, event_limit?) — artist/DJ profile (follower

capacity, area, top artists) and recent/upcoming listed events; resolves a free-text name via RA's own search if no id is given.

• ravenue(name?, venueid?, event_limit?) — venue/club profile (address,

Auth

Keyless. No account, key or payment wall.

Data sources

electronic music areas/cities, events, artists/DJs and venues/clubs. Publisher-run; this pack calls it live per request (proxy, not a mirror), so no separate reuse grant is needed.

• Resident Advisor (RA) — its own public event-listing index covering

Notes

or any personal contact data.

• Only public listing content is returned — no attendee lists, guest lists

RA's own global search index (best relevance match), so passing a direct artistid / venueid is optional but skips that extra lookup.

• raartist / ravenue resolve a free-text name to RA's numeric id via

"techno", "house", "disco", "drum-and-bass", "breaks") case-insensitively.

• raeventlistings's genre filter matches RA's own genre taxonomy (e.g.

omitted.

• raeventlistings defaults dateto to 30 days after datefrom when

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/resident-advisor/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"
    }
  }
}

Both URLs reach the same gateway and the same 1807+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

Shortened. The full README is on GitHub.