Meetup MCP server

@pipeworx/meetup

Meetup event and group search MCP — public events, groups and topic categories from Meetup, searchable by keyword, city, or group. Keyless.

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

• meetupsearchevents(query, city?, lat?, lon?, radius?, limit?) — search upcoming public events by keyword near a city (geocoded automatically) or a lat/lon point. Returns each event's title, time, URL, status, type and hosting group.
• meetupevent(eventid) — full details for one event by its numeric Meetup ID (the trailing number in a meetup.com event URL). Returns title, description, start/end time, status, type, venue and hosting group.
• meetup_group(urlname) — details for one group by its urlname (the slug right after meetup.com/, e.g. "sfpython"). Returns name, description, location, timezone, topic category and founding date.
• meetupgroupevents(urlname, limit?, includepast?) — a group's events by urlname; upcoming by default, past events with includepast: true.

None of these tools request or return attendee/RSVP lists, member lists, or any other personal contact data — deliberate, not an oversight (see "Privacy" below).

Auth

Keyless. No key, no account, no rate-limit documentation published.

Data sources

• Meetup (meetup.com), the public GraphQL API behind its own website search and event/group pages — event, group and topic-category metadata. No download file, feed or query shape is named beyond that; see src/index.ts for the route.

Privacy

Meetup's schema exposes attendee RSVPs, host identities and member lists on Event/Group. None of those fields are selected anywhere in this pack — every query here is scoped to public event/group metadata (title, time, venue, description, location) and nothing else. Keep it that way: don't add rsvps, hostRsvps, memberships, organizer, eventHosts or savedBy to any query without re-reading this note.

Gotchas

• lat/lon are required by the upstream API itself, not a choice this pack made — EventSearchFilter/GroupSearchFilter both declare them non-null. meetupsearchevents resolves a city string to coordinates via the shared resolvePlace geocoder (@pipeworx/shared, Open-Meteo-backed, keyless) before calling Meetup, so a caller never has to supply raw coordinates — but if geocoding fails to resolve a city, the tool fails loudly rather than guessing.
• radius is in miles. The upstream filter field is a bare Float with no documented unit; verified empirically against known US city radii.
• Event and group IDs are opaque strings, not always numeric-looking everywhere — eventid is the trailing path segment of a meetup.com/{group-urlname}/events/{event-id}/ URL, and a group's urlname is the slug right after meetup.com/. Neither is discoverable from the other without a lookup; meetupsearchevents and meetupgroup_events are what hand you both.
• meetupgroupevents with no events scheduled returns totalcount: 0, not an error — groups that are real and active but between events (verified live against sfpython) look identical to a dead/wrong urlname from the shape of the response alone; only meetupgroup erroring on the urlname itself distinguishes "no group" from "no events right now".
• GraphQL errors come back as HTTP 200 with a top-level errors array (standard GraphQL behavior) — this pack checks errors explicitly rather than trusting res.ok, since a malformed query or a bad ID both return 200.

Quick Start

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

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

What this endpoint actually serves

Shortened. The full README is on GitHub.