constant-watch
Related Servers
Alternatives to constant-watch
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI clients to search and ask questions over local notes, docs, and agent memories with cited answers, while also storing or retracting durable memories, exploring links, and refreshing indexes through shared MCP tools.-
- AlicenseNot gradedqualityAmaintenanceExposes a local SQLite-based memory and knowledge base as standard MCP tools, enabling AI clients to search content, recall memory fragments, and query entity relationships through natural language.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to search, retrieve, and store local memory captures, manage reminders, and access memory statistics via MCP.6 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search scattered notes and docs, ask cited questions, store or retract durable memories, explore links, and inspect or refresh the local index through shared MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to query a user's private, locally stored memories (notes, documents) with source citations, using the MCP protocol.27 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a local-first, source-cited memory layer for AI agents, with MCP tools to search, read, explain sources, and propose/apply memory updates.275 npm13Apache 2.0
TDQS
Scored across 11 tools
Several tools overlap heavily around the same daily-scoped retrieval: read_day_flow, day_sessions, and read_app_day all surface chronological day data, and recent_activity is close to day_sessions. read_review also overlaps with read_day_flow, and search_screen_memory vs ask_memory share retrieval intent, though descriptions do give useful distinguishing cues.
Most tools follow a clear snake_case verb_noun pattern (list_apps, read_observation, read_review, search_screen_memory, ask_memory, list_topics). A few nouns-first names break the pattern (day_sessions, recent_activity), but naming remains readable and largely predictable.
11 tools is well-scoped for a capture-and-recall memory server. Each tool maps to a distinct retrieval entry point (apps, observations, days, sessions, search, Q&A, topics) without obvious padding.
As a read-only observation browser, the surface is fairly complete: discovery (list_apps, list_topics), retrieval (search_screen_memory, read_*), chronological views (day_sessions, recent_activity), and NL synthesis (ask_memory). Minor gaps like export or cross-day aggregation exist but core workflows are covered.