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.2766 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read and write a personal, git-backed memory stored as plain local files, including facts, preferences, and working theories, while preserving provenance and flagging conflicts. It provides recall, remember, reflect, and amend tools over stdio or Streamable HTTP.MIT
- AlicenseNot gradedqualityBmaintenanceA zero-dependency MCP server that gives agents and people a shared inbox for submitting, listing, retrieving, and summarizing distilled dream records, with automatic redaction, hashed/signed entries, and Merkle-based inclusion and deletion proofs. Optional k-anonymous aggregation lets shared records inform system-level skills and prompts without ever editing the original text or training model weights.6 npm1MIT

litopysofficial
AlicenseNot gradedqualityCmaintenancePersistent 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.4 npm2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to store and retrieve self-hosted memories over MCP (stdio or Streamable HTTP) using local embeddings that work fully offline. Writes are redacted before they hit storage and every read is recorded in an exportable, append-only audit log.4AGPL 3.0
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.