@pipeworx/partiful

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/partiful’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 2

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.

Tools

• partiful_explore(region?) — browse the public explore page. Pass a 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_event(event_id) — full public detail for one event: title, description, start/end time, location, image, host display names, and aggregate RSVP counts. Never returns a guest list or contact info.

Auth

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

Data sources

• Partiful, public event listings — the explore carousels and per-event pages Partiful serves to any visitor, logged in or not.

Notes

• Partiful server-renders /explore and its per-event pages as a Next.js app and ships the full public-field event data inside a __NEXT_DATA__ JSON blob in the plain HTML. No separate API call, no JS execution needed — this pack parses that blob directly.
• /explore with no region carries only a small baked NYC/LA/SF trending 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.
• Only eight region codes resolve on that route (probed live 2026-10-13): 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.
• Guest lists are never exposed, structurally: an unauthenticated request to 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.
• location normalizes Partiful’s two shapes: structured (neighborhood, 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.

Tools

• partiful_explore — Browse Partiful’s public explore page — trending and themed public events (parties, pop-ups, panels, meetups) people can crash. Pass a region code for a richer, city-specific set of themed sections (H
• partiful_event — Full public detail for one Partiful event by id: title, description, start/end time, location, image, host display names, and aggregate RSVP counts (going/interested/approved — counts only, never a gu