Skip to main content
Glama
MatthewDegtyar

Claude Project History MCP Server

by MatthewDegtyar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Claude Project History MCP Server

No user-submitted related servers found.

    Related Servers

    • claude-memory

      Tim-Fischer-zh
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.
      13 npm
      4
      MIT

    • sqlite-memory-mcp

      miles990
      A
      license
      B
      quality
      D
      maintenance
      Provides persistent memory, skill tracking, failure indexing, and context sharing for Claude Code using SQLite with FTS5 full-text search.
      23
      23 npm
      1
      MIT

    • smg-claude-memory-mcp

      serkansmg
      A
      license
      B
      quality
      D
      maintenance
      Persistent, searchable project memory for Claude Code. Each project has its own local DuckDB with vector embeddings, auto-loading context at session start.
      24
      33
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.1/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose within its domain (blockers, tasks, decisions, workflows, etc.). Overlap is minimal and well-handled by descriptions, e.g., cph_decision_list vs cph_decision_search serve different intents.

    Naming Consistency5/5

    All tools follow a consistent cph_verb_noun pattern in snake_case. Prefix establishes namespace, and every name clearly indicates the action and resource, e.g., cph_task_create, cph_blocker_resolve.

    Tool Count4/5

    At 30 tools, the set is on the larger side but serves a comprehensive project history system. A couple of tools (cph_decision_attach_commit, cph_set_depth) could be internal or merged, but overall each tool addresses a legitimate need.

    Completeness5/5

    The tool surface covers the full lifecycle for tasks, blockers, decisions, and workflows, including creation, reading, updating, and deletion/closure. Additionally, it includes context management, team awareness, and activity tracking, leaving no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources