How do I install Mnemosyne OS in MCP?

To install Mnemosyne OS in MCP, start with git clone https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS. The complete step-by-step install guide for MCP is on the HOL plugin page.

Who publishes Mnemosyne OS?

Mnemosyne OS is published by Mnemosyne-OS and listed on HOL.

Mnemosyne OS

mnemosyne-os/mnemosyne-neural-os · v0.0.0 · Development & Workflow

by Mnemosyne-OS

MCP server: MIT stdio server that gives an agent the vaults the user chooses in the Mnemosyne OS desktop app, where watched folders feed separate vaults on the user's machine searched by vector and local BM25; the memory tools need the free desktop app running, and its memory engine ships closed

Install Source Claim this plugin

Follow0

Trust ScoreScan pending Security scanScan pending ComponentsScan pending

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Mnemosyne OS a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

Before you install

Sign-in: Not declared
Declared access: Not declared
License: Not declared

Check before relying on it

No security result yet. See the evidence
The publisher has not verified ownership on HOL.
No license declared in the manifest.

What is Mnemosyne OS?

Mnemosyne OS is a published development & workflow plugin for AI coding agents in the MCP ecosystem, developed by Mnemosyne-OS and distributed through the HOL AI plugin registry. MCP server: MIT stdio server that gives an agent the vaults the user chooses in the Mnemosyne OS desktop app, where watched folders feed separate vaults on the user's machine searched by vector and local BM25; the memory tools need the free desktop app running, and its memory engine ships closed.

Canonical slug: mnemosyne-os/mnemosyne-neural-os
Version: v0.0.0 · updated Oct 30, 2026
Open data: entity.json (JSON-LD)

Registry snapshot

Repository: https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS
Canonical profile: https://hol.org/registry/plugins/mnemosyne-os%2Fmnemosyne-neural-os
Owner verification: Not verified
Scanner: Registry pipeline
Security result: Not scanned
Digest verified: No

Trust and security

Provenance

Plugin root: .
Source repo: https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS
Source commit: Unpinned
Publisher verified: No
Owner verified: Not owner verified

Scanner CI check is still running

No action is required. This listing will update after the catalog rechecks scanner CI.

README badge check is still running

No action is required. This listing will update after the catalog rechecks the source README.

Security posture

See how the Trust Score is computed

Not scanned

Security result

N/A

Security score

High findings

Published advisories

None matched in GitHub security advisories, checked 2026-10-30. This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

No normalized findings were returned for this plugin.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs

Clone the repository

shell

2
Register the server in your MCP client
Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.
3
Verify the server
Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "name": "Mnemosyne-Neural-OS",
  "version": "0.0.0",
  "description": "MCP server: MIT stdio server that gives an agent the vaults the user chooses in the Mnemosyne OS desktop app, where watched folders feed separate vaults on the user's machine searched by vector and local BM25; the memory tools need the free desktop app running, and its memory engine ships closed",
  "repository": "https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS",
  "homepage": "https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS",
  "interface": {
    "displayName": "Mnemosyne OS",
    "developerName": "Mnemosyne-OS",
    "category": "Development & Workflow"
  }
}

File inventory

.codex-plugin/plugin.json

plugin-manifest

Mnemosyne OS — Frequently asked questions

What is Mnemosyne OS?: Mnemosyne OS is an AI plugin in the HOL registry. MCP server: MIT stdio server that gives an agent the vaults the user chooses in the Mnemosyne OS desktop app, where watched folders feed separate vaults on the user's machine searched by vector and local BM25; the memory tools need the free desktop app running, and…
How do I install Mnemosyne OS?: Install Mnemosyne OS in your harness: MCP — git clone https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS. Full step-by-step guidance is on the HOL plugin page.
How do I install Mnemosyne OS in MCP?: To install Mnemosyne OS in MCP, start with git clone https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes Mnemosyne OS?: Mnemosyne OS is published by Mnemosyne-OS and listed on HOL.

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here: <5; HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports: <10; Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces: <5; Workspaces that approved it or include it in an approved-plugin feed, as of today.