Mnemosyne OS
New The documentation explains every engine, step by step. docs.mnemosyne-os.io →

MCP · @mnemosyne_os/mcp

The 25 tools your agent gets.

Plug Claude, Cursor or any MCP client into the memory on your machine. The server opens one socket, 127.0.0.1:7799, and stores nothing of its own.

Plug it in

One block in your client config, or the one-click bundle for Claude Desktop:

Claude Desktop, in one click

Download the bundle and open it. If your Claude Desktop comes from the Microsoft Store, drag the file into its Extensions panel.

Mnemosyne-OS-MCP-2.1.0.mcpb · 4.3 MB

Install in Claude Desktop 
"mnemosyne": {
  "command": "npx",
  "args": ["-y", "@mnemosyne_os/mcp"],
  "env": { "MNEMO_VAULTS": "DEV,PERSONAL" }
}

The install, client by client ↗

The tools

25 in a default install. 4 more are armed by hand with an environment variable. Each row below names that variable.

The memory

Search it, ask it, write to it. Every answer is grounded in chronicles that live on this machine.

  • mnemosyne_about

    The rules it has to honor: vault protection, and what an agent may and may not do.

  • mnemosyne_vault_list

    The vaults this install exposes, with their name and chronicle count.

  • mnemosyne_memory_query

    Semantic search. Returns the chronicles themselves, for the agent to read and cite.

  • mnemosyne_memory_ask

    A question, a written answer grounded in the vault, and the sources under it.

  • mnemosyne_memory_ingest

    Write a memory that lasts: a decision, an architecture note, a session.

  • mnemosyne_memory_forget

    Erase one chronicle for good. There is no trash and no undo, so you arm it by hand.

    armed by hand · MNEMO_FORGET=1

The other agents on this machine

These three read the transcripts your coding agents already write to disk. They answer with the app closed, with no vault, and without spending a token.

  • mnemosyne_agent_collisions

    It says whether two sessions are live in the same working tree and branch. Ask before a commit.

    answers with the app closed

  • mnemosyne_agent_list

    The sessions on this machine: project, branch, model, last sign of life.

    answers with the app closed

  • mnemosyne_agent_files

    It lists the files the other sessions just wrote, with paths and times. It never returns the contents.

    answers with the app closed

The human's board

The agent reads and writes the backlog, the calendar, and its own status card on the canvas. Every write reports what it did, one operation at a time.

  • mnemosyne_todo_add

    Put tasks into the human's backlog, in order, under named steps.

  • mnemosyne_todo_list

    Read the backlog back, each task with the id needed to change it.

  • mnemosyne_todo_update

    Edit, tick off, move or archive a task, by id. An archived task comes back.

  • mnemosyne_todo_categories

    Create, rename or remove a list. A list that still holds tasks stays where it is.

  • mnemosyne_agenda_add

    Put an appointment or a deadline in the calendar, with its reminder.

  • mnemosyne_agenda_list

    Read the calendar back over a window, each event with its id.

  • mnemosyne_agenda_update

    Move it, rename it, change its reminder or how often it repeats.

  • mnemosyne_agenda_remove

    Remove an appointment, by id only. The calendar keeps no archive.

  • mnemosyne_cockpit_update

    It writes the agent's own status card on the canvas, and reads the replies left on it.

The thread of the project

These tools say where the last session stopped, what the engine linked on its own, and how the memories were classified.

  • mnemosyne_resonance_list

    The ongoing projects Mnemosyne OS tracks as workspaces.

  • mnemosyne_position_get

    Where the last session stopped, with its phase, its state and its next steps.

  • mnemosyne_position_update

    Record where this session stops, for whoever picks it up.

  • mnemosyne_git_log

    The recent commits of the active repository.

  • mnemosyne_spine_assignments

    How the memories were classified, and where the taxon ids come from.

  • mnemosyne_dream_bridges

    The links the Dream State engine found on its own while the machine sat idle.

The watch

Pheme is the reputation cartridge. These two tools say what its radar last found. The agent drafts a reply, the human posts it.

  • mnemosyne_pheme_watch

    Add or drop a subreddit or a query on the human's radar. Nothing is posted anywhere.

  • mnemosyne_pheme_radar

    What the last scan found, with the date of that scan in front.

The voice

These tools turn a script into a WAV file with a local voice, a cloned one included. They were built for voice-overs.

  • mnemosyne_voice_list

    The local engines and the voices available, a cloned one included.

    armed by hand · MNEMO_VOICE=1

  • mnemosyne_voice_speak

    Render a script to a WAV file with a local voice. A long script is split and re-assembled.

    armed by hand · MNEMO_VOICE=1

  • mnemosyne_voice_status

    Follow or cancel a render, and get the file path once it is done.

    armed by hand · MNEMO_VOICE=1

The limits

What the server can reach.

It opens one socket on the loopback. Behind it, each tool follows the route you configured. mnemosyne_memory_ask runs the model you picked, local or cloud.

Erasure and voice are absent until you arm them. Each writing tool carries its own scope. An agent sees the vaults you listed in the config, and no others.

Listed on

Where the server is listed.

Checked on 24 September 2026.

Next

Give your agent a memory.

Connect it, step by step The other npm packages