Skip to main content
Glama
meetergo

meetergo MCP server

Official
by meetergo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to meetergo MCP server

No user-submitted related servers found.

    Related Servers

    • @astrocal/mcp-server

      astrocal-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to schedule meetings via Astrocal's scheduling API, including checking availability, booking, canceling, rescheduling, and managing waitlists through natural conversation.
      46 npm
      1
      MIT

    • Google Calendar MCP Server

      SamRind
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Google Calendar by listing, creating, updating, and deleting events. It also includes functionality to find available time slots for scheduling.
      -

    • mcp-meetsync

      nicholasemccormick
      A
      license
      A
      quality
      D
      maintenance
      Integrates the MeetSync calendar negotiation API to enable AI agents to autonomously manage participants, find mutual availability, and handle meeting bookings. It exposes 19 tools for end-to-end scheduling workflows including participant preferences, proposals, and confirmations.
      19
      2 npm
      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 57 tools

    Disambiguation3/5

    Most tools follow a clear verb+resource pattern that keeps them distinct, but create_qualification_form substantially overlaps with create_routing_form since both create routing forms. The appointment tool cluster (book, reschedule, cancel, list, get, get_todays) is individually clear but numerous, and send_routing_form vs send_quick_email could cause momentary misselection.

    Naming Consistency5/5

    All 57 tools use snake_case with a consistent verb_noun structure: list_* for collections, get_* for single resources, and create_*/update_*/delete_* for CRUD operations. Exceptions like bulk_create_contacts, run_test_drive, and verify_widget_install still follow the verb-first pattern. This is exemplary consistency at scale.

    Tool Count2/5

    At 57 tools, this vastly exceeds the typical well-scoped range and exposes nearly the entire meetergo product surface. Each tool appears to serve a real function, but the sheer number creates a heavy navigation burden and makes it difficult for an agent to maintain a working model of the full set.

    Completeness4/5

    The major domains are thoroughly covered: appointments, meeting types, contacts, routing forms, webhooks, and Mira settings all have near-full CRUD/lifecycle support. Minor gaps exist — data fields have no update/delete, calendar connections are list-only, and knowledge ingestion is limited to crawling or single Q&A answers — but these are workable without agent failure.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources