Skip to main content
Glama
Marsmanleo

marsnme

by Marsmanleo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to marsnme

No user-submitted related servers found.

    Related Servers

    • shared-agent-memory

      mohammadrezafathi92-web
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to persist, retrieve, and share source-linked memory across sessions via MCP tools, backed by PostgreSQL with project/session management, decision tracking, keyword search, and cross-host context handoff.
      Apache 2.0

    • Digital Brain MCP

      dswillden
      A
      license
      Not graded
      quality
      D
      maintenance
      A persistent long-term memory system that enables AI clients to store and recall notes, code, and research via semantic search. It utilizes Google Gemini embeddings and Supabase pgvector to provide a secure, searchable 'Second Brain' for MCP-compatible applications.
      10 npm
      MIT

    • mesh-memory

      dklymentiev
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).
      1
      MIT

    • mcp-memory

      oneKn8
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.
      4
      1
      MIT

    • Second Brain

      guybr3000
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent, semantically-searchable memory for AI agents using local PostgreSQL, pgvector, and Ollama embeddings, exposed via MCP with hybrid retrieval, knowledge graph, and auto-recall hook.
      6 npm
      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.1/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: short-term vs long-term memory, different operations (insert, list, search, recall, get, demote, batch promote, etc.). No two tools overlap in functionality.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., insert_memory, list_memories, batch_promote). The single-word 'recall' is a minor deviation, and 'get_full' is slightly vague, but overall consistent.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 range, but the scope is well-defined for a memory management system. Each tool earns its place for short-term, long-term, session, and admin operations.

    Completeness5/5

    Covers the full lifecycle: insert short-term, promote to long-term, recall, retrieve, demote, expire, health checks, session boot/close. Only minor missing features like update or hard delete, which are design choices.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources