ProjectContext
Related Servers
Alternatives to ProjectContext
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA 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.12MIT
- AlicenseAqualityDmaintenanceMCP server for persistent, semantic memory across AI sessions; store context, decisions, and learnings and recall them with natural language search.227 npmMIT
- AlicenseNot gradedqualityCmaintenanceUniversal 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
- FlicenseNot gradedqualityAmaintenanceAn MCP server providing semantic vector search, dual memory engines, and Git version control for AI clients, enabling persistent memory with recall, forget, and rollback capabilities.1-
- 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
- AlicenseAqualityCmaintenanceMCP server for long-term agent memory, providing persistent memory, searchable knowledge, and evolving identity for AI agents.53Apache 2.0
TDQS
Scored across 11 tools
Each tool clearly targets either the memory resource (save/delete/update/query) or the agenda resource (create/list/get/search/update/delete). Even update_task is distinct from update_agenda as it operates on a sub-resource, eliminating any real ambiguity.
All tools follow a consistent verb_noun pattern with snake_case, using clear verbs like save, delete, update, query, create, list, get, search. The pluralization of list_agendas vs get_agenda is a minor stylistic variation but consistent throughout.
11 tools is well within the ideal 3-15 range, covering two distinct domains (memory and agenda) without bloat or thinness. Each tool earns its place in the set.
Memory has full CRUD plus semantic search, and agenda has create/read/update/delete plus task management. The only noticeable gap is the lack of a list_memories tool, but query_memory serves as a search-based alternative. Task deletion is also not available, but tasks can be added and marked complete, so the core lifecycle is covered.