Skip to main content
Glama
Nanda-Kiran

Yunaki Memory MCP

by Nanda-Kiran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Yunaki Memory MCP

No user-submitted related servers found.

    Related Servers

    • am-memory

      danielwanwx
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory for Claude Code — a self-evolving knowledge layer that survives across sessions, grows from every conversation, and surfaces relevant context automatically.
      14
      MIT

    • memory-wiki

      FloLey
      F
      license
      Not graded
      quality
      C
      maintenance
      A persistent personal memory system for Claude that accumulates and organizes knowledge over time using plain Markdown in a local git repo, providing tools for reading, searching, and capturing short-term memories.
      1
      -

    • Distributed Memory System

      jrapisarda
      A
      license
      Not graded
      quality
      C
      maintenance
      Cross-project memory for Claude Code, enabling local semantic recall and secure, git-versioned markdown storage of reusable knowledge across repositories.
      MIT

    • MCP Project Context Server

      aaronfeingold
      A
      license
      B
      quality
      D
      maintenance
      A persistent memory layer for Claude Code that maintains project information, technology stack, tasks, decisions, and session history between coding sessions, eliminating the need to re-explain project context.
      9
      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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: ingest scans and writes repo memories, repo_info shows identity, search retrieves memories, and write persists new ones. No overlap or ambiguity.

    Naming Consistency4/5

    All tools start with 'memory_' prefix, but three use verbs (ingest, search, write) while one uses a noun phrase (repo_info). This slight inconsistency is minor but noticeable.

    Tool Count4/5

    4 tools is appropriate for a focused memory MCP server. It covers the essential operations without being too few or too many.

    Completeness3/5

    Covers core operations (ingest, write, search, info) but lacks explicit update or delete functionality. The ingest tool is idempotent and can overwrite, but direct memory removal is missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources