temp-notes
Related Servers
Alternatives to temp-notes
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides persistent, cross-session memory for AI agents, allowing them to store and automatically retrieve information across different conversations and sessions without repeating context.15 npm176MIT
- AlicenseAqualityDmaintenanceProvides persistent key-value storage with full-text search, tags, and namespaces for AI agents to maintain context across sessions.7MIT
- AlicenseAqualityAmaintenanceProvides persistent, searchable memory for AI agents, enabling them to retain, recall, and reflect on information across conversations.191MIT
- AlicenseAqualityBmaintenanceA session-scoped memory layer for LLMs that enables AI assistants to explicitly store and retrieve notes, decisions, and context within a single conversation, ensuring focus without cross-session data contamination.619 npm5MIT
- AlicenseAqualityFmaintenanceA lightweight short-term memory MCP server that automatically stores and recalls working context, session state, and task progress for AI agents. Memories auto-expire after 24 hours and integrate seamlessly with workspace-aware storage across multiple projects.10MIT
- FlicenseNot gradedqualityBmaintenanceProvides persistent memory for LLM applications, enabling AI assistants to remember user preferences, facts, and conversation history across sessions.1-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: append_note adds to the note, clear_note empties it, read_note retrieves content, and write_note replaces it. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., append_note, clear_note). The naming is predictable and uniform throughout the set.
With 4 tools, this server is well-scoped for managing a single note. Each tool serves a distinct and necessary function, making the count appropriate for the domain.
The tool set provides complete CRUD-like coverage for a note-taking domain: create/replace (write_note), read (read_note), update (append_note), and delete (clear_note). There are no obvious gaps for the intended purpose.