Skip to main content
Glama
wang1051992187

@kireo/mcp-server

by wang1051992187
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @kireo/mcp-server

No user-submitted related servers found.

    Related Servers

    • Synapse Memory

      RaffaelFerro
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that provides long-term memory for LLMs by storing and retrieving important facts, decisions, and preferences through smart semantic search and automatic organization.
      12
      MIT

    • mindcore-memory-mcp

      woshilaohei
      A
      license
      A
      quality
      C
      maintenance
      A production-grade long-term memory MCP server that enables AI agents to persist and recall memories across sessions with importance weighting, confidence calibration, and efficient context window management.
      9
      1
      MIT

    • MemAI

      Filipe-Soares-de-Almeida
      A
      license
      A
      quality
      B
      maintenance
      A long-term memory MCP server for AI agents that stores memories (facts, decisions, etc.) in a single SQLite database with hybrid search and full edit history, ensuring consistency across sessions.
      24
      MIT

    • Mono Memory MCP

      potato-castle
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that provides AI assistants with a shared, persistent SQLite-backed memory for storing and retrieving project context, decisions, and discoveries. It enables cross-session continuity and team-wide knowledge sharing to keep AI coding tools aligned and informed.
      3
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct memory operation: get by ID, search by query, recall chronological feed, save new, update existing, delete, plus health check and namespace listing. Overlap between search and recall is clarified by their descriptions, making them clearly distinguishable.

    Naming Consistency5/5

    All tools follow the 'memory_<verb>' pattern consistently (memory_save, memory_search, memory_delete, etc.). The verb for listing namespaces uses two words (list_namespaces) but still fits the pattern harmoniously.

    Tool Count5/5

    8 tools is a well-scoped count for a memory management server. It covers the essential CRUD operations (save, get, search, recall, update, delete) plus auxiliary tools (health, list_namespaces) without unnecessary bloat.

    Completeness5/5

    The tool surface is complete for the domain: create (save), read by ID (get), search, chronological recall (recall), update, soft delete, plus namespace management and health check. No obvious gaps for typical memory workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources