Skip to main content
Glama
joehaddad2000

Claude Todo MCP Server

by joehaddad2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Claude Todo MCP Server

No user-submitted related servers found.

    Related Servers

    • ShackleAI Memory MCP

      shackleai
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory for AI coding tools, enabling AI assistants to store and recall project decisions, conventions, and context across sessions.
      48 npm
      MIT

    • evermemos-mcp-server

      wyh0626
      A
      license
      A
      quality
      D
      maintenance
      Enables AI coding assistants to store and retrieve persistent long-term memory across sessions, remembering project preferences, build steps, and architecture decisions.
      4
      MIT

    • MCP Memory Keeper

      emanuelele5502
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to persistently save, search, checkpoint, and restore project context across sessions, including decisions, progress, and file state. It supports shared channels, git-aware organization, and batch operations for long-running or parallel development workflows.
      250 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: TodoRead is for retrieving the task list, while TodoWrite is for replacing it entirely. There is no overlap or ambiguity between these operations.

    Naming Consistency5/5

    Both tools follow a consistent TodoVerb naming pattern (TodoRead and TodoWrite), using the same prefix and clear action verbs. This makes their functions immediately understandable and predictable.

    Tool Count2/5

    With only two tools, the server is severely limited for a todo management domain. It lacks essential operations like creating, updating, or deleting individual tasks, making it impractical for typical todo workflows.

    Completeness1/5

    The tool surface is severely incomplete. It only supports reading and full replacement of the task list, missing critical CRUD operations such as add_todo, update_todo, delete_todo, or mark_complete. This will cause frequent agent failures in managing tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources