English Français العربية

19hz

Official registry Other

19hz.info MCP.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http 19hz 'https://gateway.pipeworx.io/19hz/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "19hz": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/19hz/mcp"
        }
    }
}
NPM package @pipeworx/mcp-19hz
Claude Code 
claude mcp add 19hz -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-19hz@0.2.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "19hz": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-19hz@0.2.1"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

Environment variables

  • PIPEWORX_API_KEY secret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-19hz
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-19hz

19hz.info MCP.

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

Tools

ToolDescription
regionsList the regions 19hz covers (slug + label). Pass a slug to the events tool. Note: electronic/dance music focus (house, techno, bass, etc.).
eventsList 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.

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 1872+ 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":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "19hz": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-19hz"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-19hz

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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

Frequently asked questions

What is 19hz?

19hz.info MCP.

How do I install 19hz?

It runs as a remote server. In Claude Code: claude mcp add --transport http 19hz 'https://gateway.pipeworx.io/19hz/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does 19hz need an API key?

Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.

Is 19hz open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains 19hz?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.