Skip to main content
Glama
shivam-singh-git

recap-mcp

by shivam-singh-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to recap-mcp

No user-submitted related servers found.

    Related Servers

    • Personal Memory MCP Server

      tonyRaafat
      F
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that gives Claude (and ChatGPT/Gemini) persistent read/write access to your own memory: books, games, projects, notes, and freeform facts.
      -

    • Cortex

      ProductionLineHQ
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.
      1,036 npm
      1
      MIT

    • awhm-mcp

      juderosendev
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives Claude Code persistent, fully local long-term memory across conversations, with tools to query, log, consolidate, snapshot, and delete memories without any LLM calls.
      MIT

    • ProPlan

      King-Proplan
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for project planning inside Claude. It tracks progress, knows your codebase, and resumes exactly where you left off every session.
      12 npm
      5
      -

    • Claude-Atlas-MCP

      dcazman
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted MCP server giving Claude persistent memory via entities, observations, history, and reminders, backed by a lightweight Node/SQLite backend.
      20 npm
      1
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: project, task, session, note, or search. Even session_log and quick_note are clearly separated by structured end-of-session entries vs. stray timestamped thoughts, so an agent should rarely mis-select.

    Naming Consistency4/5

    Most tools follow a readable resource_action pattern: project_list, project_create, task_add, task_update, task_delete. A few outliers like briefing, quick_note, and search break that pattern, but the naming remains largely predictable and unambiguous.

    Tool Count5/5

    Eleven tools is a well-scoped size for a workspace/project/task/session management domain. Each tool covers a meaningful operation without unnecessary overlap or bloat.

    Completeness3/5

    Task CRUD is complete, and search/project_brief provide solid retrieval. However, project lifecycle management is incomplete: projects can be created and listed but not updated, archived, or deleted, which is notable given archived and stale project statuses are referenced.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources