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
    18 npm
    8
    Apache 2.0

Related Servers

  • memini

    lumayapartners
    A
    license
    A
    quality
    B
    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
    47 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.
    0
    MIT
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.3/5.0

Scored across 17 tools

Disambiguation4/5

Most tools have clearly distinct purposes, especially the read/write split and the issue lifecycle (log_issue, record_attempt, record_fix). A few retrieval tools (get_summary, get_context, search_events, get_issue) overlap in intent, but their descriptions provide strong usage guidance.

Naming Consistency4/5

The server uses a mostly consistent snake_case verb_noun pattern (get_*, log_issue, add_note). The main deviation is current_project, which is noun-only, and the verbs log/record/add are near-synonyms, creating slight stylistic inconsistency.

Tool Count4/5

At 17 tools, the set is slightly over the typical 3-15 well-scoped range, so it feels a bit heavy. However, the count is justified by the breadth of project memory functionality: separate read, write, issue-lifecycle, and cross-project tools.

Completeness4/5

The issue lifecycle is well covered (log, attempt, fix, read), and durable memory capture (decisions, notes, gotchas) is solid. Minor gaps exist around updating or deleting existing records, though the append-only design makes that intentional.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources