mnemos

Persist Hermes memories across sessions via MNEMOS MCP server integration.

29|7|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ncz-os/mnemos --skill mnemos-ncz-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mnemos
Source: https://github.com/ncz-os/mnemos/tree/main/integrations/hermes/optional-skills/memory/mnemos
Command: npx skills add https://github.com/ncz-os/mnemos --skill mnemos-ncz-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MNEMOS provides a persistent memory infrastructure for Hermes, enabling a shared memory pool across profiles and cross-session recall.

Core Features & Use Cases

  • Persistent cross-profile memory pool for Hermes.
  • Full-text and semantic search over memories, with knowledge-graph integration.
  • Ingestion of session transcripts and decisions for later retrieval and auditing.
  • Compression manifests and temporal validity for memory entries.

Quick Start

Configure MNEMOS as an MCP server for Hermes and point Hermes at MNEMOS_BASE to begin memory ingestion and retrieval.

Frequently Asked Questions about mnemos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable persistent cross-session memory for Hermes?

Persistent cross-session memory for Hermes is enabled by configuring MNEMOS as an MCP server and pointing Hermes at MNEMOS_BASE to start ingesting and retrieving session data.

Can I search across multiple profiles in a shared memory pool?

Yes, you can perform full-text and semantic search across multiple Hermes profiles within a shared MNEMOS memory pool, retrieving cross-profile decisions and transcripts.

What is the best way to store session transcripts for later auditing?

Storing session transcripts for auditing is handled by ingesting them into the MNEMOS pool, which applies compression manifests and tracks temporal validity for memory entries.

Does MNEMOS support knowledge-graph integration with versioning?

Yes, MNEMOS supports knowledge-graph integration with versioning, allowing you to map relationships between memories and track changes over time within the infrastructure.

How do I isolate memory namespaces for different Hermes profiles?

Namespace isolation is implemented directly within the MNEMOS MCP server registration flow, ensuring memory write and read operations remain separated across different Hermes profiles.

Why do I need a shared memory pool for cross-session recall?

A shared memory pool solves the problem of context loss between sessions by allowing Hermes to access previously recorded decisions, patterns, and transcripts across all profiles.