pickfit

BrowseMCP servers

memtomem-stm

MCP proxy that compresses and caches tool responses and surfaces prior-session memory.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python 3.12 and 3.13 supported
  1. Install via uv tool (candidate 1)

    uv tool install memtomem-stm
Where the README and reality differ
  • README: call demo__demo_search with {"query": "cache"}
    What worked: call with '{"topic": "cache"}' as advertised by tools/list (arg name is topic)

Check that it works

mms version

The output should contain “memtomem-stm 0.7.2”.

First thing to try

mms version

Add it to your agent

claude mcp add memtomem-stm -- mms
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "memtomem-stm": {
      "command": "mms",
      "args": []
    }
  }
}

Run mms version to confirm the install, then point your MCP client at memtomem-stm so it sits in front of your MCP servers.

What it does

  • Compress tool responses
    Not shown working
  • Cache repeated tool calls
    Not shown working
  • Bring up context from earlier sessions
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 3 features work
  4. Works offline

Good for

  • compress and cache repeated MCP tool responses
  • surface prior-session memory from memtomem LTM
  • add compression and observability in front of any MCP server

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 0.7.2

An MCP client handshake over stdio listed 6 tools, and a call to demo__demo_search returned a result.

Differences the test machine hit

  • README: mms init --demo --client auto as no-network first-success path
    In the test: run non-interactively with piped stdin and --no-validate, e.g. printf 'n\n' | mms init --demo --client auto --no-validate
  • README: three entry points resolve to same CLI and MCP server entrypoint
    In the test: bare `mms` with piped stdin boots the proxy as MCP server, so probe launch is simply `mms`

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.