Mnemosyne OS

Memory the human governs, on their own machine, plus what other coding agents here wrote.

Connector by Mnemosyne-OS · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 20

Chalk Labs

Need help deploying Mnemosyne OS?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/mnemosyne-os-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Memory the human governs, on their own machine, plus what other coding agents here wrote.

Use cases: agent-memory, knowledge-base

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools: 17 read · 8 write · 3 delete · 4 not yet classified
Secrets: None asked for
Install scripts: None found
Runs as: Node.js package

Tools by what they do 32

Read from the source code; the running server may list different tools.

Read 17 · Look things up without changing anything.

get_vault_info
list_chronicles
mnemosyne_agenda_list
mnemosyne_agent_collisions
mnemosyne_agent_files
mnemosyne_agent_list
mnemosyne_git_log
mnemosyne_memory_ask
mnemosyne_memory_query
mnemosyne_pheme_radar
mnemosyne_position_get
mnemosyne_resonance_list

Show 5 more tools

mnemosyne_spine_assignments
mnemosyne_todo_list
mnemosyne_vault_list
mnemosyne_voice_list
mnemosyne_voice_status

Write 8 · Create, change, send or run things.

mnemosyne_agenda_add
mnemosyne_cockpit_update
mnemosyne_dream_bridges
mnemosyne_memory_ingest
mnemosyne_position_update
mnemosyne_todo_add
mnemosyne_todo_update
write_chronicle

Delete 3 · Delete, drop, revoke or wipe things.

mnemosyne_agenda_remove
mnemosyne_agenda_update
mnemosyne_todo_categories

Not yet classified 4 · We could not tell from the name and description.

mnemosyne_about
mnemosyne_memory_forget
mnemosyne_pheme_watch
mnemosyne_voice_speak

Secrets and settings it asks for

Other settings (environment variables or headers).

MNEMO_DEFAULT_VAULT
MNEMO_SDK_PORT
MNEMO_VAULTS

Files it touches

/dev/null
/dev/stderr
/dev/stdout
Your home directory (~)
~/.mnemoforge/vault
~/.openclaw/trajectory-exports
C:\\work\\demo
C:\\work\\demo\\a.ts

Tools (32)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

get_vault_info
Returns the active vault configuration: IDE, provider, vault path, chronicle count, local AI model.
list_chronicles
List recent chronicles in the active vault. Returns filename, date, and preview.
mnemosyne_about
Re-read the server instructions: the governance tenet, the vault protection model (NORMAL and MAXIMUM, mixableWith, isolated sandbox vaults), the spine model, and the rules for an agent working on someone else's memory. Most clients show this text on connect. Call it if yours did not, or to read it again.
mnemosyne_agenda_add
Put appointments or deadlines into the user's calendar, the Agenda widget on their canvas. Use it when a conversation names a date and time to remember: a meeting, a deadline, "add this to my calendar". The app routes the write through the widget's own store, so what you file is what the user sees. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app running. To read the calendar back, change or remove an appointment, see mnemosyne_agenda_list, mnemosyne_agenda_update and mnemosyne_agenda_remove.
mnemosyne_agenda_list
Read the user's calendar back: the appointments in a time window, each with the id you need to change or remove it. Call this before mnemosyne_agenda_update and mnemosyne_agenda_remove, which both name appointments by id. The calendar has no archive and a removal cannot be undone. A repeating event appears once, with its cadence and the date of its next occurrence. Times in the answer are the user's machine local time. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app running. Scope agenda:read.
mnemosyne_agenda_remove
Remove appointments from the user's calendar. Read them with mnemosyne_agenda_list first and pass the ids. This tool matches by id only, because "remove my meetings on Thursday" is how an agent removes the wrong Thursday. There is no archive: unlike a To-do task, a removed appointment is gone, so the answer names each one it removed by title and start time for the user to check. A repeating appointment is removed as a whole series, since the calendar cannot cancel a single occurrence. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon …
mnemosyne_agenda_update
Change an appointment already in the user's calendar: move it, rename it, add or drop a reminder, start or stop it repeating. It names appointments by the id from mnemosyne_agenda_list, so call that first. A field you leave out is left alone, and passing null clears it. A start or end time that cannot be read refuses the change rather than leaving the old one quietly in place. A cadence outside daily, weekly, monthly and yearly is refused rather than turned into a one-off. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs th…
mnemosyne_agent_collisions
Check whether two agent sessions are live in the same git working tree and branch right now, across every installed harness. Call it before `git add -A`, before a commit, and before a rebase: one working tree shares one git index, so a commit from one session picks up whatever the other has staged. It answers from transcript files on disk and needs neither Mnemosyne OS nor a token. Each recorded directory is resolved to its working tree first, because one `cd` into a subfolder would make two sessions in one repository look like two projects. A clean answer covers what is readable: a session wh…
mnemosyne_agent_files
List the files other agent sessions wrote or edited recently, newest first, with the session each one came from. Paths and timestamps only. Each entry says how it is known. `recorded` means the harness logged a file-writing tool call. `from a command` means a redirection was read out of a shell command the session ran, which may never have completed. It spans every installed harness and names the agent each line came from. Use it to see what another session has already touched before you edit the same area.
mnemosyne_agent_list
List the other coding-agent sessions on this machine, read from the transcript files their harnesses already write to disk. Metadata only: conversation name, project, git branch, model, last tool, how many files were touched, and when a line was last written. It reads every harness installed here, not just your own, so you can see a session from a different agent working in your repository. Use it before you touch shared state. It reports when a line was last seen and you draw the conclusion: a crashed session and an idle one fall equally silent, so nothing here can tell you an agent is workin…
mnemosyne_cockpit_update
Update your own status card on the user's canvas, the cockpit. Call it when you start a task ("working", with a short title and status), when you need the user ("waiting"), when you are stuck ("blocked"), and when you finish ("done"). "waiting" and "blocked" make the card pulse and the taskbar flash. Send "waiting" IN THE SAME TURN as the question you ask the user, right before you stop: the harness only knows to say "waiting" for a permission prompt, and a question asked in the chat is otherwise just the end of a turn — the user never sees that you are waiting for them. Your "waiting" survive…
mnemosyne_dream_bridges
List the connections the Dream State engine found between memories while the machine was idle. Each bridge links two memories, sometimes from different vaults, with a Dream Bridge Score, a raw cosine similarity, and a short excerpt of both sides. Use it to surface associations the memory made on its own, to audit whether they are insightful or noise, or to seed creative exploration. An empty list is normal and means the engine has not produced bridges yet. It runs on idle time, when the user enables it in Settings.
mnemosyne_git_log
Read recent commits from the git repository this Mnemosyne OS is configured to read. Read-only. Each commit carries an 8-character hash, the subject line, the author and the date, newest first. The path is set on the app side, so this cannot be pointed at another checkout, and it needs the monorepo:read scope. When either is missing the answer names what is missing, rather than returning an empty list that would read as "no commits". Use mnemosyne_memory_query for the reasoning behind a change.
mnemosyne_memory_ask
Ask a question and get a prose answer grounded in the vault, plus the memories it drew on. It runs the full local RAG pipeline: deeper retrieval, lexical fusion and a re-rank. That also makes it the better retriever, so reach for it whenever you need to find something, and read the Sources list even if you ignore the prose. It is at its best on why, who and how questions that span many memories. It takes up to about 30 seconds. The prose is a model rewording of the sources, so quote the sources instead, or fetch them with mnemosyne_memory_query. Check them before you trust the answer.
mnemosyne_memory_forget
Permanently erase one memory from a vault, by id. This cannot be undone: there is no trash and no copy kept, and the memory is gone from every future retrieval. Call it only when the user asked for that specific thing to be erased in this conversation. Never to tidy up, and never to correct yourself, since memory is meant to accumulate and writing a new memory is the right fix. Never on a MAXIMUM-protection vault unless they named it. Get the id from mnemosyne_memory_query, which returns one per result. Ids are not stable across vaults, so pass the vault the id came from. This tool is present …

Show 17 more tools

mnemosyne_memory_ingest
Write a memory into a vault: a decision, an architecture note, a debug finding, a session summary. It is stored permanently and indexed for every future agent to retrieve. Use it at the end of a meaningful work session, or whenever a decision is reached that someone will want to recall later.
mnemosyne_memory_query
Search a vault and get the matching memories back word for word: notes, code, decisions, session summaries, commit history. Nothing is rewritten, so use this when you need the source text itself, to quote it or to write documentation from it. Ranking is vector similarity fused with a local BM25 channel, weighted by spine type. To FIND something rather than quote it, prefer mnemosyne_memory_ask, even when you only want its sources. It retrieves deeper and re-ranks, so it catches rare literal terms this tool misses: proper nouns, identifiers, product names. The score is not a confidence value. A…
mnemosyne_pheme_radar
Read what the user's Pheme radar last found: fresh threads in the subreddits and Hacker News queries they watch. Each thread carries a topic score, and a tier once they have run the Mnemosyne pass. The tier says how much substance they can bring to that thread. The answer leads with when the scan ran, because it is only as fresh as the last time they opened Pheme and pressed Scan. Use it to find threads to draft a reply for; the user posts it. "No radar" means no scan has been projected yet, so ask them to open Pheme and scan. Needs the app running, though Pheme itself can be closed.
mnemosyne_pheme_watch
Add a subreddit, a Hacker News search query or a topic to the user's Pheme radar, or take one off. Pheme is their reputation cartridge: it finds fresh threads worth a genuine reply. The lists belong to them. An operation that would empty one is refused. Every operation reports its own outcome: done, already there, not there, refused. The user gets a receipt in Pheme naming this agent and what changed. Use it when a conversation finds a community worth watching. It scans nothing and posts nothing; the user posts. Needs the app running, though Pheme itself can be closed.
mnemosyne_position_get
Read where one resonance was left: the phase, and the free-text note an agent or the cockpit wrote when it stopped. Read-only. It returns the resonance id, when it was saved, the spine type of the memory, and the whole note. An id nothing was ever saved under answers in plain words and points at mnemosyne_position_update, so a blank history and a failed call do not look alike. Call mnemosyne_resonance_list when you do not know the id.
mnemosyne_position_update
Record where you left off on a resonance: phase, current state, next steps. Call it at the end of a session. It is stored as a DECISION memory in the vault.
mnemosyne_resonance_list
List the resonances recorded in the default vault. A resonance is a workspace that tracks one ongoing project. Each entry carries its id, its last phase, how many minutes ago it moved, and the id of the memory behind it. Read-only. There is no status filter, so you get every resonance the scan matched in one vault, from at most 30 candidates. An empty result is written in words and means no resonance has been recorded yet. Read one in full with mnemosyne_position_get, or write a new one with mnemosyne_position_update.
mnemosyne_spine_assignments
See how Mnemosyne classified its memories. It returns the memory-to-spine assignments for one vault, newest first, and the per-spine counts for the whole vault. Use it to check whether memories landed in the right spines, to read a vault's composition at a glance, or to find the taxon ids to pass as spine_type_filter in mnemosyne_memory_query. Set include_taxonomy to also get the global spine tree.
mnemosyne_todo_add
Put tasks into the user's To-do backlog, the To-do widget on their canvas, in order and optionally under named steps. Use it when a conversation has settled what to do. Name the destination list in "list": call once without it to get the existing lists back on a LIST_NOT_FOUND answer, or pass create_list: true to make a new one. Always name a list. The app routes the write through the widget's own store, so what you file is what the user sees. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app running. To read the bac…
mnemosyne_todo_categories
Manage the lists of the user's To-do backlog: create one, rename or recolour one, remove an empty one. It is separate from mnemosyne_todo_update because these change the shape of a workspace rather than the work in it. Two refusals are worth knowing before you call. A list that still holds tasks is never removed, and you are told how many are in the way: move them first, since the app will not pick a destination on someone's behalf. The three original lists can be renamed, never removed, because their contents are what make the file readable. Works with the app closed on a dev install (the hea…
mnemosyne_todo_list
Read the user's To-do backlog back: the lists that exist and the tasks in them, each with the id you need to change it. Call this before mnemosyne_todo_update, which names tasks by id. A phrase like "delete the task about the invoice" reads perfectly and can still match the wrong task. This is also the way to answer "what is on my plate", or to check whether something is already filed before you add a duplicate. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app running. Scope todo:read.
mnemosyne_todo_update
Change the user's To-do backlog: edit a task, tick it off, move it to another list, or take it out. Every operation names a task by the id from mnemosyne_todo_list, so call that first. Removing a task archives it by default, and it can be restored. Pass permanent: true only when the user asked for it to be deleted outright. The whole batch is applied in order as one save, and each operation reports its own outcome, so a stale id does not sink the ones around it. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app runni…
mnemosyne_vault_list
List the memory vaults this Mnemosyne OS exposes, each with its token, display name and memory count. Call it first when you are unsure which vault to work against, or when the user names a store you have not seen. Pass the bold token as the `vault` argument of the other tools. The `id` line is a local path and the other tools do not take it. Vaults this server was not configured for are flagged here and refused until the user adds them.
mnemosyne_voice_list
List what can speak on this machine: the local TTS engines, installed or not, the reference voices available for cloning, and where rendered files are written. Call it before mnemosyne_voice_speak. It tells you which engine to ask for and which clone names exist, and it warns when a reference clip is too short or not mono to clone well. A clone name that does not exist is refused rather than substituted. Requires the Mnemosyne OS app to be running: the voice engines are Python sidecars inside it, and the headless daemon cannot speak.
mnemosyne_voice_speak
Render a written script to a WAV file with a local voice, including the user's own cloned voice. It is made for voice-overs: TikTok, YouTube, podcast, narration. The audio is written to disk and the path comes back, ready to drop on a video timeline. It runs offline on the local engines and sends nothing to a cloud service. This is a job rather than an instant call. Synthesis runs at roughly real time, so a 3-minute script takes 3 to 4 minutes. The tool waits a while and returns a job id if the render is still going. Poll it with mnemosyne_voice_status. Long scripts are split at sentence boun…
mnemosyne_voice_status
Check a voice render started by mnemosyne_voice_speak: how many segments are done, the time left, and, once it is finished, the path of the WAV file. Call it with no job id to list every render of this session. A render can also be stopped here. It halts at the next segment boundary and leaves no file.
write_chronicle
Write a new chronicle entry into the MnemoForge vault. Use this to record key decisions, session summaries, architectural choices. The chronicle is stored as a versioned Markdown file.

Signals

Stars: 20
Forks: 2
Open issues: 0
Contributors: 6
Weekly downloads: 132
Last commit: Oct 22, 2026 (8 days ago)
Last release: Oct 20, 2026 (10 days ago)
Last package publish: Oct 15, 2026 (15 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name: io.github.Mnemosyne-OS/mcp
Version: 2.1.3
Auth: No auth
Packages: npm @mnemosyne_os/mcp
License: MIT
Repository: github.com/Mnemosyne-OS/Mnemosyne-Neural-OS
Website: mnemosyne-os.io
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped: 50+; launches shipped
media placements: 500+; media placements
founders on every account: 2; founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get Mnemosyne OS running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Need help deploying Mnemosyne OS?

Call Get help

Cite this page

Mnemosyne OS MCP server. Agent Mart. https://agentmart.dev/connectors/mnemosyne-os-mcp (last updated 2026-10-24)

Need help deploying Mnemosyne OS?

Install

About

Reviews

Permissions

Tools by what they do 32

Read 17 · Look things up without changing anything.

Write 8 · Create, change, send or run things.

Delete 3 · Delete, drop, revoke or wipe things.

Not yet classified 4 · We could not tell from the name and description.

Secrets and settings it asks for

Network hosts it talks to 9

Files it touches

Tools (32)

Signals

Details

Rather not set it up yourself?

Get Mnemosyne OS running in your business