OptChat
Related Servers
Alternatives to OptChat
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables multiple AI agents on one machine to write, search, fetch, link, and give feedback on a shared local store of Markdown-backed facts, preferences, and conventions that persists across sessions. Memories gain confidence as different hosts confirm their use and can be distilled into denser ones, so agents stop re-discovering the same context.5507 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to share a persistent, local-first memory of architectural decisions, conventions, bug root causes, and session handoffs, searchable via full-text ranking, so context carries across tools and sessions without any cloud dependency.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to share a local-first, versioned memory of decisions, conventions, tasks, conflicts, and handoffs over MCP and REST.3 npmMIT
- AlicenseBqualityAmaintenanceEMET is an MCP memory server: persistent shared memory for AI agents, bot teams and chats. Six memory layers, verified writes (every write is read back before it is reported saved), and a separate word-for-word transcript tier. Runs locally over stdio or remotely over HTTP with OAuth, on MongoDB. One owner; optional Guest (read-only) and Member (read and write) access, both off by default.1038112 npm1MIT
- AlicenseNot gradedqualityDmaintenancePersistent, shared memory for Claude across sessions and clients (Code, Desktop, Cowork) — deterministic diff reads, checkpoints, cross-client task handoff, and project-wide search. 100% local and deterministic, no API keys, no LLM summarization.4MIT
- AlicenseCqualityBmaintenanceEnables Claude Code agents and sub-agents to share a persistent, compiled memory of project state, decisions, tasks, and facts across sessions instead of re-reading transcripts. Provides token-efficient bootstrap, search, commit, leased task claiming, and task-specific context compilation so parallel agents can coordinate without clobbering each other.59 npmMIT
TDQS
Scored across 13 tools
The eight core chat tools (status, append, view, search, thread, zoom, date, read_message) mostly target distinct operations on the message log, and the five compact_* tools are clearly fenced off as a compactor-subagent workflow. Minor overlap remains between zoom/read_message (expanding one message) and view/search/thread (locating messages), which could occasionally cause misselection.
Everything is uniformly snake_case, and the compact_* family forms a clean, predictable group of five. The core tools are single-word noun/verb hybrids (status, view, thread, date, zoom) rather than a uniform verb_noun pattern, which is readable but slightly less predictable.
13 tools is a healthy size for a chat-log server, and the core 8 cover the domain without padding. The 5 compact_* tools are a specialized subsystem that only matters to one subagent, so they add a bit of surface area for general callers.
The lifecycle is well covered: append with idempotent retries, paged view, keyword search, threading, message expansion, and a full compactor job protocol (next/read/submit/release/resume). What is missing is mutation/pruning of recorded messages and any way to enumerate sessions or chats directly, which callers must work around via search.