Practical overview
When it fits
Use it when separate agent instances need to retrieve shared vector memory, or when you are configuring an MCP memory server and can operate the required local or self-hosted infrastructure.
Who it is for
- Developers configuring persistent, searchable context for multiple Hermes Agent instances.
- Operators connecting agents running on different computers to a shared Qdrant-backed memory service.
- Users who want to configure an MCP memory server for Hermes Agent or Claude Desktop.
Documented uses
- Set up a standalone Fleet Memory node and run its documented preflight check.
- Configure an MCP server entry for an AI client.
- Choose a standalone or distributed deployment path for shared vector retrieval.
- Set a domain value for the node's memory configuration.
Requirements & limits
The repository is public and carries an MIT license. Its README describes deployments on infrastructure the operator owns rather than a shared hosted Fleet Memory instance.
- The documented stack includes Python 3.10+, FastMCP, and Qdrant.
- The standalone quickstart differs from distributed deployments, which require selecting and configuring a Qdrant endpoint.
- The project provides client configuration examples for Hermes Agent and Claude Desktop, and a registration sequence for Claude Code.
- Domain values documented by the project include work, personal, shared, and all.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a standalone node and run its preflight check
Clone the repository, initialize standalone mode, and inspect the node with the documented doctor command.
Before you start
- Python 3.10 or later, as indicated by the repository
- A local environment where the repository and its setup script can be run
Steps
Clone the repository and change into its directory.
Run the command below.
python setup.py --role standalone --non-interactiveRun the command below.
python client/fleet_memory.py --doctor
Expected outcome
The standalone setup flow has been invoked and the node's bounded preflight check has been run.
Guide limitations
- This sequence does not configure an AI client or demonstrate retrieval.
- The repository describes the doctor command as a check, not as a deployment or execution test.
Configure the MCP client for Hermes Agent
Add the documented Fleet Memory server entry to Hermes Agent configuration.
Before you start
- A local clone of the repository
- Hermes Agent configuration access
- Python 3 and the absolute path to
client/fleet_memory.py
Steps
Open
~/.hermes/config.yaml.Add an
mcp_serversentry namedfleet-memorywith commandpython3and the absolute script path as its argument.Set the
FLEET_HARD_DOMAINenvironment value to the intended domain; the README's example usesall.
Expected outcome
The documented Hermes Agent MCP server configuration is in place.
Guide limitations
- The configuration example alone does not establish that the server is connected or that retrieval works.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- amrlazw/hermes-fleet-memory · Official homepage title · retained in its source language

