Marvis Working Memory MCP

A local, persistent working-memory MCP that lets agents read rules, preferences, and project state before every task, and distill reusable experience after successful tasks.

Works with clients that support stdio MCP, including Marvis, as well as local agent frameworks that can connect to MCP. All data is stored locally in memory.json and is never uploaded to the cloud.

What it solves

• Prevents agents from forgetting confirmed work rules and preferences in new conversations.

• Lets project progress, todos, and key decisions be restored in later tasks.

• Turns successful debugging paths into experience, prioritized for reuse in similar tasks next time.

Related MCP server: mcp-chest-memory

Import into Marvis

Add the following to Marvis's MCP configuration:

{
  "mcpServers": {
    "working-memory": {
      "command": "node",
      "args": ["C:\\path\\to\\marvis-memory-mcp\\server.js"]
    }
  }
}

Add to Marvis's global rules

Put the following text at the beginning of Marvis's global instructions, assistant rules, or every automated task template:

你拥有 working-memory MCP。执行任何实质任务前，必须先调用 load_context：传入当前项目名和任务关键词。先依据返回的固定规则、长期偏好、项目状态和相关记忆规划与执行；若信息缺失或冲突，先向用户确认。

仅当用户明确确认某项长期偏好、规则、关键决定、事实或待办时，调用 remember，并传 confirmed: true；不得把你的推测写入记忆。任务出现稳定进展时调用 update_project。每个任务结束前必须调用 close_task，记录结果和下一步。

当任务最终成功、或解决了过程中出现的问题时，必须调用 record_experience：写入最终验证成功的步骤，以及“问题—解决方式”。下次相近任务开始时，使用任务关键词调用 load_context 并优先复用这些已验证经验。不得存储密码、验证码、访问令牌或私密个人数据。

Tools

First use

On first use, have Marvis record your work preferences and rules with remember, passing confirmed: true. Then, the first time each project runs, use update_project to establish project state. The data file can be backed up manually; it's recommended to make a copy before modifying it.

Important boundaries

• MCP provides stable read/write capabilities, but it cannot force Marvis to call it on its own; the "must call" constraints in global rules or task templates are still necessary.

• What is stored here is reviewable structured text; full chat logs are not saved.

Development

Requires Node.js 18 or higher. The project has no third-party dependencies:

node server.js

On first launch, a local memory.json is created automatically. The file is excluded via .gitignore to avoid committing personal memory to the repository.

License

MIT