pickfit

BrowseMCP servers

Renor

Memory for coding agents storing notes as local Markdown and serving them over MCP.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node 22
  • System packages: git
  1. install renor-engine globally via npm

    npm install -g renor-engine
    

Add it to your agent

claude mcp add renor-engine -e VAULT_PATH='<VAULT_PATH>' -- renor-engine mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "renor-engine": {
      "command": "renor-engine",
      "args": [
        "mcp"
      ],
      "env": {
        "VAULT_PATH": "<VAULT_PATH>"
      }
    }
  }
}

You fill in

  • VAULT_PATH: path to memory folder (required)

Ask the user for VAULT_PATH; pickfit never had a value, so these are placeholders.

Add renor-engine mcp as an MCP server in your agent's client settings, with the VAULT_PATH environment variable set to the folder where notes should be kept.

What it does

  • Save facts and recall them in later agent sessions
    How to use it
    1. Start the server with VAULT_PATH=<folder> renor-engine mcp and connect your agent to it.
    2. Ask the agent to save a fact with the remember_fact tool, giving a subject, predicate and object.
    3. In a new session, ask the agent to look it up with the search tool and <your query>.
    Tested
  • Keep memory as Markdown files on your computer
    How to use it
    1. Start the server with VAULT_PATH=<folder> renor-engine mcp.
    2. Ask the agent to save <your text> with the note tool. It is stored in the vault folder.
    Tested
  • Give agents access to stored memory over MCP
    How to use it
    1. Start the server with VAULT_PATH=<folder> renor-engine mcp and connect your MCP client.
    2. Ask the agent to call the search tool with <your query> to read stored memory.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • ask agent to remember something and recall it in a new session

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 1 Nov 2026
  • Version 1.3.0

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

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.