Skip to content

docs: add Perseus Vault (local-first encrypted memory via MCP) guide#691

Open
tcconnally wants to merge 3 commits into
LibreChat-AI:mainfrom
tcconnally:docs-perseus-vault-mcp
Open

docs: add Perseus Vault (local-first encrypted memory via MCP) guide#691
tcconnally wants to merge 3 commits into
LibreChat-AI:mainfrom
tcconnally:docs-perseus-vault-mcp

Conversation

@tcconnally

Copy link
Copy Markdown

What

Adds a new MCP server guide: Perseus Vault MCP, under content/docs/mcp_servers/, showing how to give a LibreChat Agent durable, encrypted, local-first long-term memory via MCP (stdio or SSE/HTTP).

Perseus Vault is open-source (MIT), local-first, and MCP-native: a single binary with encryption at rest, no cloud and no API keys. This guide gives LibreChat agents remember / recall / journal / timeline tools they call directly.

Honest framing

The guide is explicit that this does not replace LibreChat's built-in User Memory (memory:) store — that internal memory agent takes a provider/model but does not expose a pluggable storage backend or MCP hookup. Instead this attaches Perseus Vault's MCP tools to an Agent, and notes the two can coexist.

Changes

  • content/docs/mcp_servers/perseus_vault.mdx — new guide (frontmatter + <Callout> / <Steps> matching the existing Salesforce/Google Workspace pages).
  • content/docs/mcp_servers/meta.json — register perseus_vault in the sidebar pages array.
  • content/docs/mcp_servers/index.mdx — add a card linking to the new guide.

English .mdx only (source of truth), per the docs README; translations left to the workflow.

@vercel

vercel Bot commented Jul 7, 2026

Copy link
Copy Markdown

@tcconnally is attempting to deploy a commit to the LibreChat's projects Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant