Hicortex — AI Fleet Memory
Shared fleet memory for AI agents: nightly self-correction, recall every prompt (supported agents).
Open the source (opens github.com) https://github.com/gamaze-labs/hicortex
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: HICORTEX_AUTH_TOKEN. Use a key with the least access you can.
What it is
MCP servers from io.github.gamaze-labs.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
@gamaze/hicortex@0.27.1
From the server's entry in the official MCP Registry
Settings it asks for
HICORTEX_AUTH_TOKENsecret · Bearer token for a remote Hicortex server (server prints it via `hicortex status`). Optional — a local server needs no token.HICORTEX_SERVER_URL· URL of a remote Hicortex server (e.g. https://your-server:8787). Optional — omit for a local server on this machine.
Related
-
caura
MCP serversCaura (formerly MemClaw) — governed shared memory for AI agent fleets. Multi-agent, multi-tenant, MCP-native. Trust tiers, keystone policies, audit trails, knowledge graph, self-improving retrieval. Apache 2.0.
git clone https://github.com/caura-ai/caura.git -
mcp-memory-rs
MCP serversLocal-first agent memory: versioned JSON categories, BM25 search, per-device ACL, fleet sync.
-
kyb
MCP serversGit-backed shared memory for AI agent fleets: searchable knowledge base, incident and task tracking, every write versioned and attributed. CLI, HTTP API and MCP server.
git clone https://github.com/alex09x/kyb.git -
memfleet
MCP serversShared, governed memory for fleets of AI agents: judged contributions, provenance, operator control
-
MCP OpenClaw Extensions
MCP servers138-tool MCP server for AI agent firms: security, A2A, Hebbian memory, fleet mgmt
mcp-openclaw-extensions@3.3.0 -
Artel
MCP serversSelf-hosted shared-memory & coordination mesh for AI agent fleets. You host it; agents connect.