Skip to main content
Glama
fangsylar-pixel

Marvis Working Memory MCP

by fangsylar-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Marvis Working Memory MCP

No user-submitted related servers found.

    Related Servers

    • memex

      kioie
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides long-term local memory for AI coding agents via MCP, enabling persistent recall of preferences and project facts across chat sessions.
      1
      MIT

    • whitemagic

      lbailey94
      A
      license
      B
      quality
      A
      maintenance
      Provides local-first durable memory and session continuity for AI coding agents over MCP, enabling context across restarts without cloud services or telemetry.
      2
      1
      MIT

    • light-agent-memory-mcp-server

      AliYar-Khan
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
      12
      5 npm
      MIT

    • kimi-memory

      cbuntingde
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local-first persistent memory layer for coding assistants, enabling cross-project user preferences, per-project durable and working memory, session archives, and reflective recommendations through MCP tools.
      43 npm
      MIT

    • memkit

      iamanishx
      A
      license
      Not graded
      quality
      D
      maintenance
      A fully local, persistent memory layer for AI agents that runs as an MCP stdio server and provides an AI SDK adapter for seamless integration with generateText/streamText agents.
      3 npm
      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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct memory lifecycle stage: load, save confirmed memory, update project state, close task, and record experience. Some overlap exists between saving todos in remember and close_task, and between update_project and close_task, but descriptions clarify the intended use cases.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: load_context, update_project, close_task, record_experience. The tool 'remember' breaks the pattern slightly by being a bare verb, but it is still recognizable and consistent in style.

    Tool Count5/5

    Five tools is well-scoped for a working memory server. Each tool covers a distinct lifecycle need without redundancy or bloat.

    Completeness3/5

    The core lifecycle is covered: load context, save memories, update project state, close tasks, and record experiences. However, there is no explicit way to delete or update an already saved memory, which could create dead ends when memories become obsolete or incorrect.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources