Partiful MCP server

@pipeworx/partiful

Public event listings from Partiful's explore pages — titles, times, locations, host names, and aggregate RSVP counts for the parties, pop-ups, panels and meetups Partiful surfaces as crashable.

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

region code (nyc, la, sf, dc, chi, bos, atx, mia) for a richer set of themed sections for that city; omit it for the top-level cross-city trending overview (NYC/LA/SF only).

• partiful_explore(region?) — browse the public explore page. Pass a

description, start/end time, location, image, host display names, and aggregate RSVP counts. Never returns a guest list or contact info.

• partifulevent(eventid) — full public detail for one event: title,

Auth

Keyless. No account, login, or API key of any kind — the explore page and event pages are rendered for anonymous visitors.

Data sources

pages Partiful serves to any visitor, logged in or not.

• Partiful, public event listings — the explore carousels and per-event

Notes

and ships the full public-field event data inside a NEXTDATA__ JSON blob in the plain HTML. No separate API call, no JS execution needed — this pack parses that blob directly.

• Partiful server-renders /explore and its per-event pages as a Next.js app

overview (~5 events per city). The per-region explore page is a separate, much richer per-city page with up to a dozen themed sections (Halloween Parties, Pop-Ups & Markets, Meet Someone New, etc.) — use it when you want real coverage for one city.

• /explore with no region carries only a small baked NYC/LA/SF trending

nyc, la, sf, dc, chi, bos, atx, mia. Every other candidate tried (chicago, seattle, london, philly, houston, san-diego, denver, atlanta, nashville, portland, toronto, …) 404s. There is no broader city/geo query parameter — this is the whole surface Partiful exposes.

• Only eight region codes resolve on that route (probed live 2026-10-13):

an event page gets guest: null from Partiful itself, so there is nothing to leak even if this pack tried to surface it. Host display names (shown publicly on the event page to any visitor) are returned; host photos, phone numbers, emails, and RSVP-form answers are never surfaced.

• Guest lists are never exposed, structurally: an unauthenticated request to

display name, address lines, a Google Maps link) and freeform (a single address string). A private/unlisted event, or an id that never existed, both 404 cleanly — partiful_event raises a clear error rather than returning a half-filled record.

• location normalizes Partiful's two shapes: structured (neighborhood,

Quick Start

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

{
  "mcpServers": {
    "partiful": {
      "url": "https://gateway.pipeworx.io/partiful/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/partiful/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.

Shortened. The full README is on GitHub.