Skip to main content
Glama
lightning-llc-jpn

mustdo-mcp

Official
by lightning-llc-jpn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mustdo-mcp

No user-submitted related servers found.

    Related Servers

    • icloud-mcp

      jerrydjin
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that bridges Claude Desktop to iCloud Mail, Calendar, Reminders, and Contacts, enabling cross-service actions like daily briefs, scheduling, email drafting, task deferring, and unified search via a single prompt.
      34 npm
      MIT

    • Kairos

      itskylebrooks
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables Claude to read and, where permitted, safely write Apple Calendar, Reminders, Contacts, Notes, Mail, and Music data on macOS over stdio without Full Disk Access. It includes guarded changes, activity logging, undo, and optional Music play history.
      260 npm
      MIT

    • calendar-mcp

      p-l-ta
      A
      license
      A
      quality
      C
      maintenance
      MCP server that gives Claude and other MCP hosts full access to Calendar.app on macOS — list, search, create, update, and delete events across all configured accounts.
      7
      34 npm
      1
      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.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct operation: auth (sign_in, get_me), CRUD (add/update/delete/list_todo), and special status actions (complete_todo, snooze_todo). The only mild overlap is that update_todo can also change status, but the description explicitly redirects recurring occurrences to complete_todo/snooze_todo, keeping boundaries clear.

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout: sign_in, get_me, add_todo, update_todo, complete_todo, snooze_todo, delete_todo, list_todos. No mixed conventions or vague verbs.

    Tool Count5/5

    8 tools is well-scoped for a personal TODO server. Auth, account info, CRUD, and recurring-occurrence actions each earn their place without redundancy.

    Completeness4/5

    Covers the full TODO lifecycle including soft delete, completion, snooze, recurrence, and listing with filters. Minor gaps: no restore-undelete, no single-todo get, and no explicit unsnooze, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources