Skip to main content
Glama
KovaMind

Kova Mind MCP Server

Official
by KovaMind

Related Servers

Alternatives to Kova Mind MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Gives Claude Desktop, Cursor, Cline, and other MCP-compatible AI tools persistent memory, enabling them to store and recall information seamlessly across sessions.
      4 npm
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to access a shared portable vault for memory, skills, and API credentials through MCP, so tools can store and retrieve memories, read versioned skill playbooks, and make server-side API calls without exposing secret keys.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to retain persistent, searchable memory and versioned vaults, spawn and recall named agents with state and audit history, run automations, monitors, and deep research, and execute on-chain and web tasks across sessions. It can be installed alongside Claude Code, Cursor, Windsurf, Zed, Hermes, and other MCP clients, with vault and memory optionally run entirely on the user's machine.
      45
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to persistently remember user preferences and context through client-side encrypted vaults, ensuring memory is portable and private across different MCP clients.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables personal AI memory management through MCP tools for adding, searching, exporting, and deleting memories, with knowledge-graph retrieval and multi-hop association for clients like Claude Desktop and Cursor.
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools are clearly grouped by domain (memory vs vault), and within each group, actions are distinct. However, memory_extract vs memory_recall could confuse agents about when to extract vs recall. Overall, most tools have well-defined boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with a domain prefix (memory_ or vault_). Snake_case is used uniformly, making the naming predictable and easy to navigate.

    Tool Count5/5

    With 12 tools covering two distinct subsystems (memory and vault), the count is well-scoped. Each tool serves a clear purpose without unnecessary bloat or deficiency.

    Completeness4/5

    The memory subsystem covers extraction, recall, reinforcement, and novelty scoring but lacks explicit deletion or listing of all memories. The vault subsystem covers setup, unlock, store, find, handles, execute, and lock, but could benefit from a credential update or delete operation. Minor gaps exist but core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive