Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-19hz Show me upcoming house music events in London."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
19hz.info MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| List the regions 19hz covers (slug + label). Pass a slug to the events tool. Note: electronic/dance music focus (house, techno, bass, etc.). |
| List upcoming electronic/dance music events for a 19hz region. Optionally filter by keyword (matches title, venue, genre, or artist) and a date window. Returns normalized events sorted by date. |
Related MCP server: Nightlife Search
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"19hz": {
"url": "https://gateway.pipeworx.io/19hz/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/19hz/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, 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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about 19hz data" })The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/19hz_regions \
-H 'Content-Type: application/json' \
-d '{}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/19hz_regions. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This server cannot be deployed
Search events, conference weeks, cities, venues and artist schedules via remote MCP.
Search MusicBrainz artists, releases, works, labels; resolve ISRC/ISWC/barcode; fetch cover art.
Google Events listings with dates, venues, and ticket links via a hosted MCP server.
European and US event data from Eventbrite: dates, venues, categories, ticket prices, organizers.