Skip to main content
Glama
riponcm

Projectmem

by riponcm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Projectmem

  • MCP-Mem0

    yellnuts
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    A robust server for managing long-term agent memory using Mem0, providing efficient storage and retrieval of agent memories with a lightweight Python-based implementation.
    MIT
  • Memstate AI - Agent Memory System by memstate-ai

    Memstate AI - Agent Memoryofficial

    memstate-ai
    A
    license
    A
    quality
    D
    maintenance
    Provides versioned, structured memory for AI agents, allowing them to store facts, detect conflicts, and track knowledge history via a hosted SaaS platform. It enables efficient hierarchical information retrieval and semantic search while keeping token usage constant as memory scales.
    7
    21 npm
    8
    Apache 2.0

Related Servers

  • memini

    lumayapartners
    A
    license
    A
    quality
    C
    maintenance
    Local-first project memory for AI coding agents. Records failed attempts, fragile files, and decisions per repo, and warns the agent via hooks before it repeats a recorded mistake.
    6
    59 npm
    MIT

  • cogmem

    dcondrey
    A
    license
    A
    quality
    F
    maintenance
    Self-improving, verifiable memory for AI coding agents. Learns how you work, stops repeating mistakes, models each project, recalls the right lesson at the right moment. Every memory is signed and tamper-evident. Local-first.
    8
    2
    Apache 2.0

  • beadless

    KuraPiee
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI coding agents with git-native persistent memory and a dependency-aware task graph, letting them record and fuzzy-recall architectural decisions, lessons, and gotchas while creating, claiming, and completing tasks that auto-unblock downstream work. Stores everything as plain JSON and Markdown committed inside the repository, so context stays branch-aware, team-shared, and reviewable in pull requests.
    9 npm
    MIT
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A4.1/5.0

Scored across 17 tools

Disambiguation4/5

The read tools (get_summary, get_context, search_events, get_issue) all retrieve memory but are distinguished by scope and budget in their descriptions. list_projects vs current_project is a minor overlap but clearly differentiated (reachable vs resolved project). Write tools each target a distinct event type (issue/attempt/fix/decision/note).

Naming Consistency4/5

Predominantly consistent verb_noun snake_case: get_*, list_*, search_*, record_*, add_*, precheck_*. The lone deviation is current_project, which is noun-only with no verb. Otherwise the pattern is predictable and readable.

Tool Count4/5

17 tools is slightly above the typical 3-15 sweet spot, but each tool maps to a distinct memory operation (12 reads, 5 writes). The read/write split justifies the count, though it leans heavy.

Completeness4/5

Covers the full memory lifecycle: project discovery, reading summary/instructions/map/plan/context, issue logging, attempt/fix recording, decisions, and notes, plus cross-project gotchas and scoring. No update/delete tools exist, but decisions are deliberately append-only and plan edits are done by editing files directly, so gaps are minor and by design.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources