Developer-tools MCP server
Mnemosyne OS
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 18
- 9
- 4
- 0
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @mnemosyne_os/mcp@2.4.0
- Registry
- npm
- Published
- Nov 14, 2026
- Integrity
sha512-3QGTfazyTK7fbzxQK5yK3RK5AG3fKe2lZFNV/GYeXI1mgn4FG91iBMwx3uYPT8whZr2e7gtxtVU0YfeFxDtRNA==- Analyzer
- modelara v0.1.8 · policy not recorded
31 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
mnemosyne_aboutmnemosyne-os-mcp:tool:mnemosyne_aboutObserved interface and hashesRe-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. Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agenda_addmnemosyne-os-mcp:tool:mnemosyne_agenda_addObserved interface and hashesPut 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. Input schemasha256:8509d1f029a60c8134129b492b110fa2f7d7888b562615508cc1e45e0c56a7d2Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agenda_listmnemosyne-os-mcp:tool:mnemosyne_agenda_listObserved interface and hashesRead 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. Input schemasha256:691e565ad7b6809ee3c60a535b7db7f79dc65614209ec3216300d9f786fade5aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agenda_removemnemosyne-os-mcp:tool:mnemosyne_agenda_removeObserved interface and hashesRemove 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 and needs the app running. Scope agenda:write. Input schemasha256:837ec7b54c8cf8ecb837e1bb0c4ac6065fba68e17334c2c12447ab7b64fcb3dfOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agenda_updatemnemosyne-os-mcp:tool:mnemosyne_agenda_updateObserved interface and hashesChange 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 the app running. Scope agenda:write. Input schemasha256:52c9f830919d17ae76db9f6262fc045f6828f11d09187bc6ffef7a8dabee924fOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agent_collisionsmnemosyne-os-mcp:tool:mnemosyne_agent_collisionsObserved interface and hashesCheck 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 whose transcripts live elsewhere does not appear at all, and sessions whose harness records no directory are listed separately as unplaceable. Input schemasha256:67ec2469eac7d533a9b1ed0e9bb50bc4558d5487fffdefef0fc6db8afaf9df7eOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agent_filesmnemosyne-os-mcp:tool:mnemosyne_agent_filesObserved interface and hashesList 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. Input schemasha256:742cb9b409bd76f23324aa7f2ee675995e1a4c063fe57819324656f568b058dfOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_agent_listmnemosyne-os-mcp:tool:mnemosyne_agent_listObserved interface and hashesList 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 working. Works with the Mnemosyne OS app closed. Input schemasha256:ce47040435d1ffa4cf84e33f6760d5e3154de9f3778584176239ca93447969d9Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_cockpit_updatemnemosyne-os-mcp:tool:mnemosyne_cockpit_updateObserved interface and hashesUpdate 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" survives the harness saying the turn ended. You declare the state; the app prints it next to the time since your last call, so keep calling at real milestones or the card goes quiet. The answer carries any message the user left on your card. Read it and act on it. Needs the app window open. This is a card, so nothing is stored in memory. Input schemasha256:5961cee2a6026483736f487477d98b60871da385c1341ad59c93d232d70e9e42Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_dream_bridgesmnemosyne-os-mcp:tool:mnemosyne_dream_bridgesObserved interface and hashesList 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. A side marked "inferred" was matched on its id and spine type in the only vault that fits (older scans did not record the vault): likely, not certain. 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. Input schemasha256:cacb820e5dbe9b1d90df6ba2bda41a93c052bc2a81ec0bcb683823ce55471f63Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | 2.3.0 | |
mnemosyne_git_logmnemosyne-os-mcp:tool:mnemosyne_git_logObserved interface and hashesRead 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. Input schemasha256:c6897737bbb82548cae9c30485e24722c1022b6877a0bbcede4cde86a1b74b0aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_mac_update_checkmnemosyne-os-mcp:tool:mnemosyne_mac_update_checkObserved interface and hashesmacOS only. Check whether a newer Mnemosyne OS is published and what an update would do, without writing anything. It reads the installed version in /Applications, the latest release manifest (latest-mac.yml), the macOS version, whether the app is running, and whether the key files exist (never their content). Works with the app closed. Call it before mnemosyne_mac_update_install and show its answer to the person. Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.4.0 | 2.4.0 | |
mnemosyne_mac_update_installmnemosyne-os-mcp:tool:mnemosyne_mac_update_installObserved interface and hashesmacOS only. Install the latest Mnemosyne OS release in place of the one in /Applications, the way a careful person would. It downloads the dmg and checks its size and sha512 against latest-mac.yml, copies keys.enc, keys-transfer.json and model-config.json to ~/.mnemosyne/update-backups/<time>/, asks the app to quit and waits for its own shutdown (it never kills it), copies the new app beside the old one, verifies its signature, swaps them (the old app goes to the backup folder) and relaunches. It stops at the first refusal and says which. Works with the app closed. After it, macOS asks the PERSON for Keychain access: tell them to click Always Allow; never click it for them. Needs the exact version mnemosyne_mac_update_check reported and confirm: true. Input schemasha256:056c9ea9b647997f7da55f36500e30b07514bec49588e60f0a59544cda4cfe42Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.4.0 | 2.4.0 | |
mnemosyne_memory_askmnemosyne-os-mcp:tool:mnemosyne_memory_askObserved interface and hashesAsk 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. Input schemasha256:cacd45599fae73e58bc949f9bc962b7075c5d8b08bd3e618d7fb5632bc91c50eOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_memory_ingestmnemosyne-os-mcp:tool:mnemosyne_memory_ingestObserved interface and hashesWrite 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. Input schemasha256:7a513e7229578bedb45721bc2d246678f3462d06f12baa394d98df9c178d808cOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | 2.4.0 | |
mnemosyne_memory_querymnemosyne-os-mcp:tool:mnemosyne_memory_queryObserved interface and hashesSearch 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 hit and a miss come back with similar numbers, so judge the text, not the number beside it. Input schemasha256:bbd2f7858e3f129ac815f3b9b962754fca320ddff4389eaba90cf30cff3dbd4bOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | 2.4.0 | |
mnemosyne_pheme_radarmnemosyne-os-mcp:tool:mnemosyne_pheme_radarObserved interface and hashesRead 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. Input schemasha256:cd351a8e2e46b20e615c2f036c83d5d5634a160f027657a51e84357a0b47e409Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_pheme_watchmnemosyne-os-mcp:tool:mnemosyne_pheme_watchObserved interface and hashesAdd 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. Input schemasha256:91a4e561cff93307503857a34a10eb12ac4548199387ac21d0e429db8e3d1048Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_position_getmnemosyne-os-mcp:tool:mnemosyne_position_getObserved interface and hashesRead 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. Input schemasha256:305b54f82aceffae59e38aaf12412661817863c7d53c1e5855c309debd989dfbOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_position_updatemnemosyne-os-mcp:tool:mnemosyne_position_updateObserved interface and hashesRecord 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. Input schemasha256:e5b3b64be127e7bb7e9c2683e5025c346a3502e55eb88cb76b5683aff8c235b7Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_resonance_listmnemosyne-os-mcp:tool:mnemosyne_resonance_listObserved interface and hashesList 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. Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_review_getmnemosyne-os-mcp:tool:mnemosyne_review_getObserved interface and hashesRead one review as it stands: its state (waiting / approved / changes / rejected), every answer so far, and its publishing state. Does not wait. Needs the Mnemosyne OS app RUNNING: on macOS its window may be closed (the app stays up and the host reads the file); on Windows and Linux closing the last window quits the app, so it must be open. Scope review:ask. Input schemasha256:825759c03e63ba246e169f46670d4875a20a0105d2912a4992a8d8c3dd50c1dbOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.0 | 2.3.0 | |
mnemosyne_review_openmnemosyne-os-mcp:tool:mnemosyne_review_openObserved interface and hashesAsk the human to review a video or image you produced. It shows in the review panel of Mnemosyne OS and, when the human paired the review bot, on their phone (Telegram) with Approve / Change / Reject buttons. Returns the review id: pass it to mnemosyne_review_wait. The file must be an absolute path inside ~/.mnemosyne/generations, ~/.mnemosyne/voiceovers or ~/.mnemosyne/outbox (copy a render there first); anything else is refused with OUTSIDE_SEND_FOLDERS. For a retake of a review, pass its id as parentId: the panel shows the versions side by side. Needs the Mnemosyne OS app RUNNING: on macOS its window may be closed (the app stays up and the host reads the file); on Windows and Linux closing the last window quits the app, so it must be open. Scope review:ask. Input schemasha256:948dad377e4ad45c59b22eb41a1b4b03f25a3db16545cdae42e38ed45338e0c9Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.0 | 2.3.0 | |
mnemosyne_review_waitmnemosyne-os-mcp:tool:mnemosyne_review_waitObserved interface and hashesWait for the human's answers to ONE review (from mnemosyne_review_open), from the app or from their phone. Returns every answer given after `after`, oldest first: verdict approve / changes / reject, or null for a plain comment (the human can send frame notes alone, without a verdict), plus the text (a voice note arrives transcribed) and the second of the video it points at when they gave one. From the app an answer can carry frame notes: exact frame numbers (counted at the fps shown), each with what to fix there. Pass `after` (the createdAt of the review, or the `after` the last result told you) so an answer given before you started waiting is not missed. ONE CALL WAITS AT MOST ~45 s, so it never outlives your client's own tool timeout. When it returns STILL WAITING, nothing was decided: call it again with the same id and the same after, in a loop, for as long as you mean to listen. The human sees in the panel whether an agent is listening. Needs the Mnemosyne OS app RUNNING: on macOS its window may be closed (the app stays up and the host reads the file); on Windows and Linux closing the last window quits the app, so it must be open. Scope review:ask. Input schemasha256:e1a2f9de4c3e2eb57ae10ddeb151d2bcd7c5dd808d454e5232915f6da0fb8060Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.0 | 2.3.0 | |
mnemosyne_spine_assignmentsmnemosyne-os-mcp:tool:mnemosyne_spine_assignmentsObserved interface and hashesSee 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. Input schemasha256:2aca328576fe6e0ee03dd319d70f60ab1610c5e2b6798b3321bc0e1213d5a94bOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_telegram_sendmnemosyne-os-mcp:tool:mnemosyne_telegram_sendObserved interface and hashesSend one local file (video, photo, audio, pdf) to the user's Telegram home chat — the same Hermes bot channel they already configured. Use it when a render or export finished on disk and the user is not at the machine: pass the absolute path, optionally a short caption. The recipient is NEVER chosen by you: only TELEGRAM_HOME_CHANNEL from the assistant .env. Caps: 48 MB, allow-listed types (mp4/mov/webm/mkv, jpg/png/webp/gif, wav/mp3/ogg, pdf). Needs the Mnemosyne OS app RUNNING: on macOS its window may be closed (the app stays up and the host reads the file); on Windows and Linux closing the last window quits the app, so it must be open. Refusals: NO_TELEGRAM (bot or home chat missing), TOO_LARGE, BAD_TYPE, NOT_A_FILE, BAD_REQUEST. Input schemasha256:54fdb3b51f68fd4a2d13627e9d0427601e1fec372ebf14a79ba144185993a037Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.0 | 2.3.0 | |
mnemosyne_todo_addmnemosyne-os-mcp:tool:mnemosyne_todo_addObserved interface and hashesPut 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, and file one plan into ONE list, its steps as "group". Write each text as a short title a person can say aloud (about 80 characters); the detail goes in "description". A rule, a trap or a decision is not something to do: file it with kind "note", so it stays as context and counts in no total. On a recent app your tasks wait in « To triage » until the human keeps them, and each gets a number (#42) shown by mnemosyne_todo_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 backlog back or change what is in it, see mnemosyne_todo_list, mnemosyne_todo_update and mnemosyne_todo_categories. Input schemasha256:4bb0fa2f081aaafc9d702034147c75847bb85a94ef2f0a114f250094c4a844abOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_todo_categoriesmnemosyne-os-mcp:tool:mnemosyne_todo_categoriesObserved interface and hashesManage 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 headless daemon reads the file); an npm install has no daemon and needs the app running. Scope todo:write. Input schemasha256:889e0787cdb1130f06d4443f2ee2ac8f9f8e1a2eba97d3be5a4dc09dcd30f031Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_todo_listmnemosyne-os-mcp:tool:mnemosyne_todo_listObserved interface and hashesRead the user's To-do backlog back: the lists that exist (the person may call a list a category or a project) and the tasks in them, each with the id (and the short number, #42) you need to change it, its status, priority, whether it is a note or waits in triage, and the names of its attached files. Call this before mnemosyne_todo_update, which names tasks by id or number. 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. Without list, the answer opens with the tasks that need attention (overdue, due within 7 days, high priority, in progress), each with its reason: answer from those first. 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. Input schemasha256:0f3d0c99174958db2d5d9ea9de12eef5b3965bb6c32ee1f8caaaf980ac45381bOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | 2.3.0 | |
mnemosyne_todo_updatemnemosyne-os-mcp:tool:mnemosyne_todo_updateObserved interface and hashesChange 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 running. Scope todo:write. Input schemasha256:63b95ab2be2396cba5e402e27d85cb46829740dea967c2dd585415ef0e697959Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | No change observed | |
mnemosyne_vault_listmnemosyne-os-mcp:tool:mnemosyne_vault_listObserved interface and hashesList the memory vaults this server can reach, each with its token, display name, memory count and, when the owner wrote one, a line on what it holds. 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. A vault outside this server's grant is never named here; the note under the list, when there is one, says how the user grants it. Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.2.0 | 2.4.0 |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 2.3.0 2.4.0FAIL2 added0 removed2 schema0 write1 destructive0 unknown
- 2.2.0 2.3.0FAIL4 added0 removed2 schema3 write0 destructive0 unknown