Skip to content

[Feature]: Expose Hermes memory (MEMORY.md/USER.md) via MCP server #10835

@easyvibecoding

Description

@easyvibecoding

Feature Description

hermes mcp serve exposes 10 conversation/messaging tools but zero memory tools. Users running Hermes alongside Claude Code, Cursor, or other MCP clients have no way to share persistent memory between agents.

Proposed Solution

A lightweight FastMCP stdio server that exposes:

  • Memory CRUD — read, add, replace, remove entries in MEMORY.md/USER.md with proper §-delimited section handling and char limit enforcement
  • Session browsing — list recent sessions, read transcripts, FTS5 search across all past sessions
  • Safety — atomic writes, file locking (cross-platform), prompt-injection scanning (aligned with tools/memory_tool.py)

This enables a dream consolidation workflow: review past sessions → extract insights → persist to memory → prune stale entries.

Use Case

Any multi-agent setup where Hermes coexists with Claude Code or other MCP-compatible tools. Currently the only way to bridge memory is manual copy/paste between agents.

Additional Context

Implementation PR: #10833 (will be replaced with a properly templated PR)

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low — cosmetic, nice to havetool/mcpMCP client and OAuthtool/memoryMemory tool and memory providerstype/featureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions