John CEO Agentic Memory
Related Servers
Alternatives to John CEO Agentic Memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server providing agents with persistent working, episodic, and semantic memory backed by CockroachDB, exposed via tools to store, recall, list, and forget memories.MIT
- FlicenseNot gradedqualityBmaintenanceProvides persistent, globally-distributed memory for AI agents using CockroachDB's MCP Server and AWS S3 backups, with session isolation, audit trails, and full-text search.-
- AlicenseAqualityDmaintenanceMCP server for semantic code indexing using vector embeddings, enabling AI agents to maintain persistent memory of codebases through natural language queries and intelligent chunking.193 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMulti-tenant memory system MCP server with vector search, relationships, and trust-based access control for AI assistants.157 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server providing semantic memory storage and retrieval using vector embeddings powered by LanceDB and Google Gemini. It supports multi-tenant isolation and bucket-based organization for managing structured memories through natural language queries.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides persistent semantic memory backed by PostgreSQL and pgvector for storing and searching thoughts via vector embeddings. It enables dimensional organization, conflict detection, and historical tracking of facts, decisions, and observations.1 npmAGPL 3.0
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: write persists, search retrieves, recall_context packs, forget maintains. There is no overlap in functionality, reducing risk of misselection.
All tools follow a consistent memory_verb pattern (memory_write, memory_search, memory_recall_context, memory_forget). The naming is predictable and uniform, simplifying agent tool selection.
Four tools is a tightly scoped set that covers the core memory operations without redundancy. Each tool earns its place, fitting the recommended 3-15 range.
The set covers the full memory lifecycle: create/write, retrieve/search, recall context for injection, and forget/maintenance for updates and deletions. No obvious gaps for the stated purpose of persistent user memory.