Marvis Working Memory MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Marvis Working Memory MCP Load my context for the current task."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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: light-agent-memory-mcp-server
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
Tool | When to call |
| Before every task starts |
| After the user explicitly confirms information should be kept long-term |
| When project state changes in a stable way |
| Before every task ends |
| After a task succeeds, especially after debugging |
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.jsOn first launch, a local memory.json is created automatically. The file is excluded via .gitignore to avoid committing personal memory to the repository.
License
Available Tools
5 toolsclose_taskB
每个任务结束前调用,记录结果与待办,供下一次任务开始时加载。
Inputs: outcome (required), project (required), next_actions.
load_contextA
每个任务开始时必须先调用。读取用户长期偏好、固定规则、指定项目状态与相关已确认记忆。
Inputs: query, project.
record_experienceA
当任务在遇到问题后最终成功,或首次验证一条可复用流程后调用。保存成功步骤和问题解决方式;同一项目、同一任务会更新为最新经验。不得记录密码、验证码、访问令牌、个人隐私或其他秘密。
Inputs: task (required), successful_workflow (required), project, problems_and_fixes.
rememberB
保存用户明确确认的长期偏好、规则、关键决定、事实、待办或笔记。不要保存模型推测;必须传 confirmed: true。
Inputs: type (required), content (required), confirmed (required), project.
update_projectA
更新当前项目的状态、摘要与下一步;适合任务进行中出现稳定进展时调用。
Inputs: status (required), project (required), summary, next_actions.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct memory lifecycle stage: load, save confirmed memory, update project state, close task, and record experience. Some overlap exists between saving todos in remember and close_task, and between update_project and close_task, but descriptions clarify the intended use cases.
Most tools follow a clear verb_noun pattern: load_context, update_project, close_task, record_experience. The tool 'remember' breaks the pattern slightly by being a bare verb, but it is still recognizable and consistent in style.
Five tools is well-scoped for a working memory server. Each tool covers a distinct lifecycle need without redundancy or bloat.
The core lifecycle is covered: load context, save memories, update project state, close tasks, and record experiences. However, there is no explicit way to delete or update an already saved memory, which could create dead ends when memories become obsolete or incorrect.
Maintenance
Related MCP Connectors
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Persistent memory for AI agents across Claude, ChatGPT and any MCP client.
Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides long-term local memory for AI coding agents via MCP, enabling persistent recall of preferences and project facts across chat sessions.1MIT
- AlicenseAqualityDmaintenanceProvides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.129 npmMIT
- AlicenseBqualityBmaintenanceProvides local-first durable memory and session continuity for AI coding agents over MCP, enabling context across restarts without cloud services or telemetry.1MIT
- AlicenseAqualityCmaintenanceProvides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.8MIT