Skip to main content
Glama
Sign In
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
      A
      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.
      12
      479 npm
      MIT

    • Meeting Scheduler

      joecheofficial
      A
      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.
      MIT

    • pim-mcp

      da-the-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables an agent to read and manage calendars across Nextcloud, iCloud, Google and any CalDAV server, merging every account into one sorted view. Exposes tools for listing and searching events, finding free time, and creating, updating or deleting events, with secrets kept out of the config.
      8
      394 npm
      MIT

    • 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
      29 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

    A3.9/5.0

    Scored across 54 tools

    Disambiguation4/5

    Tools are organized by resource+action and are largely distinct (e.g. create/get/update/delete for webhook, agent, calendar, event). A few boundaries are soft — get_calendar_context vs list_events vs get_availability, and create_connection_link vs create_booking_page could momentarily confuse — but descriptions clarify them well.

    Naming Consistency5/5

    Uniform snake_case verb_noun convention throughout (list_agents, create_event, update_webhook, delete_calendar, get_availability). Consistent verbs (get/list/create/update/delete/cancel) with no camelCase or style mixing.

    Tool Count2/5

    54 tools is very heavy for a single MCP server and will strain tool selection. While the breadth (agents, calendars, events, webhooks, proposals, availability, iCal, keys, booking pages, links) partly justifies it, several resources push the surface well past a comfortable scope.

    Completeness4/5

    Near-complete lifecycle coverage across all domains: full CRUD for agents, calendars, events, webhooks, iCal subs, and booking pages, plus proposal flow, availability rules, scoped keys, audit, and usage. Minor gaps like no update_booking_page or update_connection_link, but workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources