Repository navigation
v0.18.0
Minor: two optional parameters are added, and one output field. No tool, no
existing parameter and no annotation is removed, renamed or retyped; a call that
passes neither parameter sends the same request as before.
Added
-
memory_writetakessupersedes. An optional array of 1 to 32 distinct
memory_idvalues (opaque strings) of memories this write corrects or replaces.
It is forwarded to the memory service, which stores the new memory and marks
every listed one as replaced in a single transaction: all of it or none. It is
not accepted in shared rooms (xroom:domains). The ids are checked here
before anything is sent (an empty list, more than 32, a repeat or an empty
string is refused by the tool's schema; the format of an id is not checked,
since this package treats ids as opaque, and the service re-validates it). -
memory_writereports what it replaced. When the write replaced at least
one memory, the text gains a lineReplaced: <ids>andstructuredContent
gainssuperseded: string[](declared inoutputSchema, optional). Nothing
is added for an ordinary write. When the answer does not confirm every id that was
passed, a further line,Not confirmed as replaced: <ids>; they may still appear in reads., names the rest;supersededstays what the service confirmed. -
Refused replacements say why, in the agent's terms. A 400 for a room
domain ("In a shared room a correction is written next to the old memory;
replacing is not supported."), a 404 for an id not found in this account's
memory, and a 409 naming the id, the reason and, when there is one, the memory
that already replaced it. These three answers print only those fields of the
service's reply, with no raw tail. A refused write that carriedsupersedes
also says that nothing was replaced. -
memory_readtakesinclude_history. An optional boolean, forwarded when
passed. It also returns memories that a later write replaced, each marked
replaced by <id>in the text and withsuperseded_byinstructuredContent
(an optional field ofmemory_read's items;memory_list_recent's items are
unchanged). It makes replaced memories eligible under normal ranking and
top_k; it is not a promise of the complete history. Whether replaced
memories are hidden from an ordinary read depends on the account's setting,
and thememory_readdescription says only that. -
Descriptions say the same thing in both cases.
memory_write's description
now ends with one clause pointing atsupersedes.memory_read's sentence
about corrections no longer says the earlier memory is never hidden: without
supersedesit stays as it was; with it, it is marked replaced, hidden from
reads when the account hides replaced memories, and returned by
include_history. -
npm: https://www.npmjs.com/package/@mnemoverse/mcp-memory-server
-
MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers?search=mnemoverse
What's Changed
- feat(tools): memory_write supersedes, memory_read include_history by @izgorodin in #247
- release: v0.18.0 by @izgorodin in #248
Full Changelog: v0.17.2...v0.18.0