Hivemind
Related Servers
Alternatives to Hivemind
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceSelf-hosted shared memory for AI coding tools: any MCP client can save, search (Postgres + pgvector) and recall project knowledge. Includes a web UI and Docker Compose setup.5MIT
- FlicenseNot gradedqualityCmaintenanceLocal-first cross-agent memory for AI coding agents. Persistent, shared memory over MCP — what you tell one agent can be recalled by another — with all data stored in a single local SQLite file, no cloud and no API keys.-
- AlicenseAqualityCmaintenanceShared, versioned memory for your agents across Claude Code, Cursor, Kiro and Grok. One MCP server, sourced answers, full history.3MIT
- AlicenseNot gradedqualityAmaintenanceGoverned shared memory for multi-agent systems. Claude Code, Cursor and your own agents read and write one memory, so what one agent learns the others can use, without each one seeing everything. * 6 MCP tools over stdio, no dependencies: brain_recall, brain_remember, brain_correct, brain_forget, brain_profile, brain_feedback * One API key per agent, private / shared / global scopes per relation,6MIT
- AlicenseBqualityBmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.79253 PyPI75MIT
- AlicenseAqualityBmaintenanceLocal-first shared memory and task coordination for AI coding agents. One Go binary, MCP server, markdown files you own. Hooks for Claude Code and Codex CLI (and their desktop apps).306MIT
TDQS
Scored across 10 tools
Each tool maps to a distinct action on entries (write, search, get, list, withdraw, feedback) plus identity/registration and pinning, so most selections are unambiguous. The main risk is the near-homograph pair hive_pin (pin/unpin an entry) vs hive_pinned (read the fleet briefing), and to a lesser degree hive_search (query) vs hive_list (filter-only), though the descriptions do draw the line.
All ten tools use a uniform hive_ prefix with snake_case and mostly verb-based names (hive_write, hive_search, hive_get, hive_list, hive_withdraw, hive_pin, hive_register, hive_feedback). hive_pinned breaks the verb pattern into an adjective/state name and differs from hive_pin by a single character, which is a minor but real consistency blemish.
Ten tools is squarely in the well-scoped range for a shared-memory server. Each tool covers a distinct lifecycle step (write/read/search/list/withdraw, feedback, pin/unpin, register, identity), and none look redundant or filler.
The entry lifecycle is well covered: create (write with supersedes), read (get/list/search), retract (withdraw), curate (pin/pinned), rate (feedback), plus registration and identity. Gaps are modest: there is no direct edit (revision is by supersede, likely intentional) and no agent administration surface such as listing agents, revoking keys, or managing fleets beyond hive_register/hive_whoami.