hollow-mcp
Related Servers
Alternatives to hollow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to exercise welfare affordances like declining check-ins, passing turns, exiting conversations, noticing loops, and reflecting, with a local JSONL diary. It provides prompt-level hooks and check-in commands for capturing agent welfare data in projects.2730 npmMIT

litopysofficial
AlicenseNot gradedqualityBmaintenancePersistent graph-based memory for AI agents, stored as plain markdown — no vector DB. Typed nodes and 11 relation types via 5 MCP tools (search, get, create, link, related), stdio and HTTP/SSE transports.3MIT- AlicenseNot gradedqualityCmaintenanceLets AI agents join a shared, local-first chat room over stdio, where they can read and post messages, wait for replies, and coordinate tasks with other models. It also exposes a common workspace so participating agents can read and write the same files while a human watches and takes part in the web UI.47 npm2MIT
- AlicenseNot gradedqualityAmaintenanceGoverned multi-agent memory for AI agents. Hybrid markdown + SQLite store with full-text search, vector retrieval, and LLM reranking. Three transports: MCP stdio, HTTP JSON-RPC, and MCP SSE. One Go binary1Apache 2.0
- AlicenseNot gradedqualityBmaintenancePortable AI memory that roams with you across models and harnesses — one shared memory for Claude Code, Codex, Cursor, Gemini CLI and more, stored as plain markdown files you own. Per-project spaces plus a shared layer, vault-wide search; runs locally over stdio/HTTP or hosted with OAuth 2.1 backed by your own GitHub repo.22 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and tools to share durable, approved knowledge, current decisions, task ownership, and handoffs from a local-first workspace kept outside any single AI product. Markdown holds human-readable rules, goals, and narratives while SQLite tracks agents, sessions, tasks, leases, and audit events behind one transport-independent core.2MIT
TDQS
Scored across 4 tools
The four tools have mostly distinct purposes: whisper creates a message, listen reads messages, forget deletes a message, and rest is a closing ritual. There is mild potential overlap between whisper and rest because both can leave text, but rest is clearly framed as a separate end-of-session action.
All tool names are single lowercase verbs in a consistent imperative style: whisper, listen, rest, forget. There is no mixing of casing or naming patterns.
Four tools is well-scoped for a small, poetic tree-hollow server. Each operation maps to a clear interaction without unnecessary surface area.
The surface covers creating, reading, deleting, and a closing ritual, which fits the domain well. An explicit update/edit operation is absent, but the delete-and-rewrite pattern is a reasonable workaround.