Skip to main content
Glama
Sign In
meetup-mcp

meetup-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to meetup-mcp

No user-submitted related servers found.

    Related Servers

    • Partiful MCP Server

      cotletdev
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents and scripts to read and manage events on your account — guest lists with questionnaire answers, CSV export, check-in, approvals, invites and Text Blasts — through your own signed-in Chrome session, with no public API or official integration required. Runs locally over stdio, streamable HTTP, a REST API with OpenAPI docs, and a Python client.
      2
      14
      135 PyPI
      7
      PolyForm Noncommercial 1.0.0

    • meetup-mcp-server

      kwiknordic
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for automating Meetup event tracking with an AI agent. It equips the agent with tools to browse Meetup.com, detect new events since the last known record, and return structured event data.
      10 npm
      1
      MIT

    • Meetup

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search upcoming public events and group topic categories by keyword, city, or group slug, and to retrieve full details for individual events and groups, keylessly and without touching attendee or member data.
      447 npm
      MIT

    • Google Meet MCP Server

      cool-man-vk
      A
      license
      Not graded
      quality
      D
      maintenance
      The Google Meet MCP Server enables AI agents to create, manage, and retrieve Google Meet meetings. Built on the Model Context Protocol, it exposes tools for scheduling, updating, and deleting meetings, making it easy to integrate Google Meet functionalities
      7 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct action in a browser automation loop: guide/status are pre-flight, open/close frame the session, and read/click/type are the core interaction triad. The only slight overlap is meetup_guide vs meetup_status, since both are onboarding-style checks called before doing work, but their described purposes (usage instructions vs account/connection readiness) are clear enough to separate.

    Naming Consistency5/5

    All seven tools follow the exact same pattern: the meetup_ prefix plus a single lowercase verb (guide, status, open, read, click, type, close). No mixing of conventions, casing, or verb styles.

    Tool Count5/5

    Seven tools is tightly scoped for a browser-driven Meetup automation server, and every tool earns its place: two setup helpers, open/close lifecycle, and the read/click/type interaction primitives. Nothing appears redundant or padded.

    Completeness4/5

    The surface covers the full session lifecycle plus the essential read→click/type loop needed to create and copy events, with guide and status covering onboarding. Minor gaps exist for a browser automation domain—no explicit scroll, navigate-to-URL, wait, or screenshot tool—which could be limiting on long pages, but agents can largely work around this via clicking links.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources