mcp-19hz
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
mcp-19hz
19hz.info MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1861+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
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: mcp-bandsintown
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"19hz": {
"url": "https://gateway.pipeworx.io/19hz/mcp"
}
}
}What this endpoint actually serves
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 1861+ 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
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":"..."}.
Run it from npm
@pipeworx/mcp-19hz is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/19hz/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"19hz": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-19hz"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
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.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Search events, conference weeks, cities, venues and artist schedules via remote MCP.
Search events, conference weeks, cities, venues and artist schedules via remote MCP.
Manage Eventbrite events, ticket classes, venues and discounts; read attendees, orders and reports.
Run events by text: create events, sell tickets, approve guests, invite people, find events.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides music events, concerts, music festivals, nightclubs and other events information.172MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Bandsintown for artist events and global event listings. It supports natural language queries through the Pipeworx gateway.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying San Francisco Bay Area events from Funcheap, including event details, tags, and categories.79 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables discovery of electronic/dance events, concerts, and festivals across North American metros, with location lookup by city, state, or coordinates.97 npm1MIT