Skip to main content
Glama
Zehee

Kimi Code Memory MCP Server

by Zehee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Kimi Code Memory MCP Server

No user-submitted related servers found.

    Related Servers

    • agent-memory

      jcyamacho
      F
      license
      Not graded
      quality
      F
      maintenance
      Persistent memory for MCP-powered coding agents, allowing LLMs to remember preferences, project context, and decisions across sessions via Markdown files.
      8 npm
      -

    • RepoRecall

      esannkv
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.
      MIT

    • ecc-memory

      ElisaBit-UG
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to persist and recall cross-repository memories as Markdown files via save, search, read, and health-check tools, with local-only storage and no cloud services.
      4 npm
      MIT

    • ai-memory-mcp

      chen789654
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to retain memory across sessions by storing conversations locally in Markdown files, allowing personalization and continuity without external servers.
      MIT

    • Distributed Memory System

      jrapisarda
      A
      license
      Not graded
      quality
      D
      maintenance
      Cross-project memory for Claude Code, enabling local semantic recall and secure, git-versioned markdown storage of reusable knowledge across repositories.
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 22 tools

    Disambiguation4/5

    Tools cluster into clear groups (memory CRUD, context loading, theme management, workspace maintenance) and each has a distinct action/target. Some pairs like search vs search_context or organize_memories vs bootstrap_workspace could require careful reading, but descriptions resolve the boundaries.

    Naming Consistency4/5

    Almost all names follow a lowercase verb or verb_noun pattern (remember, list_tags, trace_theme, sync_workspace_index). A few generic single-verb names like list, delete, and move are less descriptive but still stylistically consistent.

    Tool Count3/5

    At 22 tools, this sits in the heavy range, and the server spans several subdomains (memory, context, themes, workspace admin). Each tool has a plausible purpose, but the set feels broader than a tightly scoped memory server.

    Completeness4/5

    Memory entries have full lifecycle coverage (create/read/search/list/update via overwrite/delete/move), and themes/context are well supported. Minor gaps remain around removing a single turn from a theme or enumerating sessions, but agents can generally accomplish core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources