meetergo-mcp
Related Servers
Alternatives to meetergo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that exposes the Orita scheduling API as tools for AI agents, enabling them to look up event types, book appointments, and manage bookings.37 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Watermelon.ai that exposes all 13 public API endpoints as tools, enabling AI assistants to manage contacts, conversations, messages, custom fields, and webhooks.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes 17 Google Workspace APIs (e.g., Gmail, Drive, Calendar) as auto-generated tools for AI assistants, enabling natural language control of Google services.-
- AlicenseNot gradedqualityFmaintenanceProvider-agnostic CalDAV calendar MCP server that connects any CalDAV calendar to AI assistants, enabling calendar operations like listing, creating, updating, and deleting events.AGPL 3.0
- AlicenseAqualityBmaintenanceMCP server for Google APIs — Gmail and Calendar tools for LLM agents.62MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Proton privacy suite — Mail, Pass, Drive, Calendar, and VPN. 36 tools for Claude and other MCP-compatible AI agents.20MIT
TDQS
Scored across 37 tools
Each tool has a clearly distinct purpose. There is no overlap between create_booking, create_one_time_booking_link, and other booking-related tools. Even similar operations like cancel_appointment and reschedule_appointment are clearly differentiated.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_contact, list_appointments, update_meeting_type). There are no mixed conventions or vague verbs.
With 37 tools, the server is on the higher side but still reasonable for a comprehensive scheduling and CRM system. Each tool covers a specific operation without redundancy, but the count is slightly above the ideal range.
The tool set covers most CRUD operations for core resources (contacts, appointments, meeting types, routing forms, webhooks). Minor gaps exist, such as missing delete for meeting types and data fields, but the overall surface is substantial and functional.