pickfit

BrowseMCP servers

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+
  1. npm install -g @pcircle/memesh and doctor

    npm install -g @pcircle/memesh && memesh doctor

Check that it works

memesh --version

The output should contain “4.11.5”.

Add it to your agent

claude mcp add memesh -- memesh-mcp
JSON 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 sessions
    How to use it
    1. Ask your agent to call the message tool with action "send", a project, a sender, a recipient and your message text as the payload.
    2. Optionally pass an idempotency_key so the same message is not sent twice.
    Tested
  • Leave handoffs for the next session
    How to use it
    1. Ask your agent to call the task_state tool with your project name.
    2. Fill in the goal, the next step and anything blocking the work.
    Tested
  • Save preferences across sessions
    How to use it
    1. Ask your agent to call the remember tool with a note describing your preference and the project it applies to.
    Tested
  • Share project decisions across agents
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 3 of 4 features work
  4. 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

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.