MeMesh
Local layer letting AI coding agents share memory and exchange tasks.
Tested on Linux
Use it
Linux x86_64
You need first
- Runtimes:
Node.js 22.13+
npm install -g @pcircle/memesh and doctor
npm install -g @pcircle/memesh && memesh doctor
Check that it works
memesh --versionThe output should contain “4.11.5”.
Add it to your agent
claude mcp add memesh -- memesh-mcpJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"memesh": {
"command": "memesh-mcp",
"args": []
}
}
}Add memesh-mcp as an MCP server in your AI coding client, then its tools (remember, recall, message, task_state and others) become available to the agent.
What it does
- Send tasks between AI coding sessionsTested
How to use it
- Ask your agent to call the
messagetool with action "send", a project, a sender, a recipient and your message text as the payload. - Optionally pass an idempotency_key so the same message is not sent twice.
- Ask your agent to call the
- Leave handoffs for the next sessionTested
How to use it
- Ask your agent to call the
task_statetool with your project name. - Fill in the goal, the next step and anything blocking the work.
- Ask your agent to call the
- Save preferences across sessionsTested
How to use it
- Ask your agent to call the
remembertool with a note describing your preference and the project it applies to.
- Ask your agent to call the
- Share project decisions across agentsNot shown working
How far pickfit got
Linux x86_64
- Installs
- Connects
- 3 of 4 features work
- Works offline
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 4.11.5
An MCP client handshake over stdio listed 12 tools, and a call to recall returned a result.
Differences the test machine hit
- README: probe shows no required args for remember/recall/task_state/briefing
In the test: pass explicit project string e.g. project=verify-proj for remember, task_state, briefing and message send; empty {} calls return tool error - README: message discover lists running sessions
In the test: use message action=send with project, sender, recipient, payload and idempotency_key for durable local delivery; action=discover alone returns tool error when no live sessions