Skip to main content
Glama
Chronary

Chronary

Official
by Chronary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Chronary

No user-submitted related servers found.

    Related Servers

    • SavvyCal MCP Server

      OfirOhan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover bookable time slots, book and cancel meetings, list events, and enable or disable scheduling links. Also supports managing webhooks and exposes write/destructive operations with MCP annotations so clients can confirm before acting.
      71 npm
      MIT

    • Meeting Scheduler

      josephtandle
      F
      license
      Not graded
      quality
      D
      maintenance
      Automates 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.
      -

    • Calendly MCP Server

      thenavidm
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents and CLIs to work with Calendly accounts through 66 tools — 44 reads and 22 writes requiring explicit confirmation — covering event types, availability, booking invitees, contacts, custom fields, Notetaker recaps and transcripts, organizations, memberships and webhooks, across multiple privately configured scoped token or OAuth accounts.
      66
      58 npm
      AGPL 3.0
    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

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources