Skip to main content
Glama
extrei

project-memory-mcp

by extrei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to project-memory-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-memento

      Bogeymanlicitness496
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding assistants with persistent memory storage using a local SQLite database. Enables tools to remember project details, notes, and relationships across sessions to maintain context and reduce repetitive explanations.
      17
      4
      MIT

    • LumenCore

      arclightdynamics
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.
      7 npm
      Apache 2.0

    • Agent Progress Tracker MCP

      thesammykins
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to track, search, and retrieve their progress across projects with persistent memory using SQLite storage and LLM-powered summarization. Supports logging completed work, searching previous entries, and retrieving context for multi-step or multi-agent workflows.
      6 npm
      MIT

    • Memory MCP Server

      bsahane
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store, search, and manage persistent memories, todos, kanban boards, reminders, and progress trackers in a local SQLite database.
      1
      Apache 2.0

    • Memory MCP

      nerdyaustin
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.
      8
      1
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: recording, searching, and summarizing project memory. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Names follow a predictable resource-prefixed pattern: memory_record, memory_search, project_status. The pattern is readable and consistent enough, though project_status is more of a noun phrase than an action-oriented name.

    Tool Count5/5

    Three tools is well-scoped for a focused project-memory server. Each tool earns its place and the surface is small but not underwhelming.

    Completeness4/5

    Core memory workflows are covered: recording, searching, and checking status. A minor gap is the lack of a get-by-id or full-text retrieval tool, since search only returns excerpts; deletion is handled indirectly via supersede.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources