Skip to main content
Glama
AlekseiMarchenko

Central Intelligence

by AlekseiMarchenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Central Intelligence

No user-submitted related servers found.

    Related Servers

    • Recall

      rvreddy24
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store and semantically retrieve durable memories across sessions via MCP or REST, with tools for remembering, recalling, asking, updating, and forgetting memories.
      5 npm
      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

    • memento-mcp-server

      jee1
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with persistent, human-like memory infrastructure via MCP, enabling them to store, search, summarize, and forget episodic, semantic, procedural, and working memories across sessions.
      859 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.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: context for broad bootstrapping, recall for specific queries, remember for writes, forget for deletes, and share for scope changes. The context/recall distinction is especially well-handled with explicit usage guidance for each.

    Naming Consistency4/5

    All tool names are single lowercase words following a consistent imperative style (remember, recall, forget, share). The only minor deviation is 'context', which is a noun rather than a verb, though it still fits the single-word pattern.

    Tool Count5/5

    Five tools is well-scoped for a persistent memory system. Each tool covers a distinct operation (load context, store, search, delete, share) and none feel redundant or unnecessary.

    Completeness4/5

    The core memory lifecycle is covered: write (remember), read (context/recall), delete (forget), and scope management (share). The only minor gap is the lack of an explicit update operation, though the descriptions acknowledge this by recommending forget-then-remember for corrections.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources