A
licenseNot graded
qualityB
maintenanceEnables AI agents to list scheduled Calendly events, check availability for event types, and create single-use scheduling links.
358 npm
MIT
Chronary
Officialby Chronary
Related Servers
Alternatives to Chronary
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes Cal.com scheduling tools to AI agents via MCP, enabling listing event types, checking availability, and managing bookings (create, cancel, reschedule).-
- FlicenseNot gradedqualityDmaintenanceAutomates meeting logistics with tools for scheduling, availability checking, slot finding, timezone conversion, and recurring date generation. Eliminates the need for custom calendar logic by providing validated time operations and formatted invitations for applications and AI assistants.-
- AlicenseNot gradedqualityCmaintenanceWraps the Calendly API v2 for scheduling data, enabling AI agents to query and manage Calendly events and availability.5 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables natural language interaction with Google Calendar through AI agent tools for scheduling, event management, and availability checking.-
- AlicenseAqualityDmaintenanceIntegrates 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.192 npmMIT
TDQS
A4/5.0
Scored across 54 tools
Disambiguation5/5
Each resource family (agents, calendars, events, booking pages, webhooks, proposals, iCal subscriptions, scoped keys) has a clearly distinct purpose and consistent verb_noun actions. Nearby tools like get_availability vs find_meeting_time and hold-event creation vs confirm/release are distinguished by explicit scope and lifecycle descriptions.
Naming Consistency5/5
Tool names follow a highly consistent snake_case verb-first pattern across all resource families: create_, get_, list_, update_, delete_, cancel_, confirm_, release_, respond_to_, resolve_, set_, clear_, subscribe_, sync_. Even exceptions like accept_terms and find_meeting_time still fit the predictable verb-noun style.
Tool Count2/5
54 tools is far above the typical 3-15 tool MCP sweet spot and exceeds the 25+ threshold for a heavy surface. The count is not padded with near-duplicates, but it makes the server feel like a full REST API rather than a curated agent-facing toolset, increasing tool-selection burden.
Completeness4/5
The major lifecycles are well covered: agents, calendars, events, webhooks, proposals, iCal subscriptions, connection links, and scoped keys all have the necessary creation, reading, update, and deletion operations where applicable. The main gap is booking pages, which have create/list/get/delete but no update/settings mutation, though this does not create a dead-end workflow.
Maintenance
ActivityStale
ResponsivenessNo issues