mcpField
P
Predicthq

Predicthq

Remote
pipeworx.ioBusiness & Marketing0Updated 5w ago

About Predicthq

Predicthq is an MCP server that wraps the PredictHQ Events API for event discovery and demand-forecasting inputs. It is intended for users examining event details or likely activity near a location, with local and Pipeworx gateway options.

Key features

  1. 01Search events by query and filters
  2. 02Find events near coordinates
  3. 03Retrieve event details by ID
  4. 04Rank results by predicted impact

Use cases

  1. 01Explore events within a date range
  2. 02Check activity near a venue or store
  3. 03Review an event’s attendance and location
  4. 04Use event signals for demand forecasting

MCP support

Exposes PredictHQ event search, nearby-event lookup, and event-detail tools to MCP clients. It can run locally over stdio or connect through the Pipeworx gateway.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/predicthq/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-predicthq

PredictHQ MCP — wraps the PredictHQ Events API (predicthq.com)

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
search_eventsSearch the PredictHQ Events API for real-world events (concerts, sports, conferences, festivals, public holidays, severe weather, etc.) used for demand forecasting. Filter by free-text query, category, country, and an active-date window; results are ranked by predicted impact. Returns each event with its rank, predicted attendance, dates, and location. Example: search_events({ query: "taylor swift", country: "US", category: "concerts", start: "2026-06-01", end: "2026-12-31" }).
nearby_eventsFind PredictHQ events within a radius of a geographic point (latitude/longitude). Useful for "what is happening near this venue/store/airport" demand-forecasting queries. Filter by category and active-date window; results are ranked by predicted impact. Example: nearby_events({ latitude: 40.7128, longitude: -74.006, radius: "10km", category: "concerts,sports" }).
get_eventFetch a single PredictHQ event by its id, returning its title, category, rank, predicted attendance, dates, and location. Example: get_event({ id: "abcDEF123" }).

Quick Start

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

{
  "mcpServers": {
    "predicthq": {
      "url": "https://gateway.pipeworx.io/predicthq/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/predicthq/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 1683+ 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/predicthq_search_events \
  -H 'Content-Type: application/json' \
  -d '{"query":"marathon","country":"US","category":"sports","start":"2026-06-01","end":"2026-12-31"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/predicthq_search_events. 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": {
    "predicthq": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-predicthq"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-predicthq

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 Predicthq data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.