Skip to main content
Glama
pasichDev

Docket

by pasichDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Docket

No user-submitted related servers found.

    Related Servers

    • Todo MCP

      peterfabakker
      A
      license
      Not graded
      quality
      D
      maintenance
      A persistent todo list server that enables AI assistants to manage tasks across different platforms using the Model Context Protocol. It provides tools for creating, listing, updating, and deleting todos with support for priorities, tags, and due dates.
      MIT

    • synco-mcp

      ijustseen
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.
      -

    • sprinter

      danimoya
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted backlog tracker with priority scoring and an MCP server, enabling AI agents to autonomously pull, work on, and update tasks via JSON-RPC tools.
      MIT

    • Task Manager MCP Server

      sidibie1
      F
      license
      A
      quality
      C
      maintenance
      A small Model Context Protocol (MCP) server that lets an AI assistant manage a to-do list on your behalf.
      4
      -

    • USRCP

      frank-bot07
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server providing a shared, AES-256-GCM encrypted SQLite ledger of structured user state (stack, projects, preferences) that any MCP-aware tool can read/write, with user-held keys and optional zero-knowledge sync.
      1
      Apache 2.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.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct action in the todo lifecycle: add, list, edit, claim, release, complete, delete, history, and version. Even close concepts like release and complete are clearly differentiated in their descriptions, so there is little risk of an agent selecting the wrong tool.

    Naming Consistency4/5

    All tools share the consistent todo_ prefix and use snake_case with single-word command names. Most are verb-based (add, edit, claim, release, complete, list, delete), but history and version are noun-based, which is a minor deviation from the otherwise predictable pattern.

    Tool Count5/5

    Nine tools is well within the ideal range for this domain and each tool serves a clear, non-redundant purpose. The count feels neither too thin nor bloated for a shared todo-list server.

    Completeness5/5

    The tool set provides full CRUD coverage (add/list/edit/delete) plus lifecycle actions for claiming, releasing, and completing items. The history and version tools add useful diagnostics, and there are no obvious missing operations that would block an agent from managing todos end-to-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources