Forgetful
Related Servers
Alternatives to Forgetful
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA persistent memory server for AI agents using MCP protocol, enabling semantic storage and retrieval of dialogues, documents, and agent states.-
- AlicenseAqualityDmaintenanceMCP server for persistent, semantic memory across AI sessions; store context, decisions, and learnings and recall them with natural language search.238 npmMIT
- AlicenseNot gradedqualityDmaintenancePersistent semantic memory server for AI assistants via MCP, enabling long-term context retention and semantic search across conversations.12MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that provides semantic memory storage and retrieval for coding and AI agents, enabling durable context across chat sessions.4-
- AlicenseNot gradedqualityDmaintenanceUniversal MCP server providing adaptive semantic memory for AI agents, supporting document ingestion, semantic search, chat persistence, cross-project linking, and cloud storage overflow.3GPL 3.0
- AlicenseAqualityDmaintenanceMCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.915 npmMIT
TDQS
Scored across 3 tools
The three tools form a clean meta-pattern: discovery, documentation, and execution each have a distinct role, and the execute tool's description enumerates the vast underlying tool surface. The only mild overlap is between discover_forgetful_tools and how_to_use_forgetful_tool, both of which return tool information, though one is a list/browse and the other is deep per-tool docs.
All three names are snake_case and share a consistent '<verb>_forgetful_tool(s)' suffix, making the family immediately recognizable. Minor deviations occur: 'how_to_use' is a phrase rather than a single verb, and the singular/plural suffixes (tools vs tool) are inconsistent across the three.
Three tools is thin on its face, but this is a deliberate gateway/dynamic-tool pattern where execute_forgetful_tool fronts dozens of memory, project, entity, document, and artifact operations, so the small top-level surface is appropriate rather than impoverished. Each of the three tools clearly earns its place with no redundancy.
The underlying surface described in the execute documentation covers near-full lifecycle: create/get/update/query/obsolete and linking for memories, CRUD-ish operations for projects, entities, documents, and code artifacts, plus entity-memory and entity-project linking. Hard deletes and cross-resource search are the only plausible gaps, and discovery-plus-execute means the surface is self-revealing rather than dead-ending.