pickfit

BrowseMCP servers

ai-cortex

Local store giving coding agents codebase maps, session history, and typed memories via MCP.

Use it

Before you install: known vulnerabilities

pickfit found 10 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:protobufjs 6.11.6 Arbitrary code execution in protobufjs (GHSA-xq3m-2v4x-88gg, critical, fixed in 7.5.5)
  • npm:sharp 0.32.6 sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591 (GHSA-f88m-g3jw-g9cj, high, fixed in 0.35.0)
See 8 more

Linux x86_64

You need first

  • Runtimes: Node.js 20 or newer
  1. install ai-cortex via npm

    npm install -g ai-cortex
Where the README and reality differ
  • README: MCP tools listed as recall_memory(worktreePath), record_memory(worktreePath), index_project etc
    What worked: actual MCP schemas use `path` for index_project and `task` for suggest_files (probe truncated names); calling with worktreePath/query gives Invalid arguments

Check that it works

ai-cortex --version

The output should contain “ai-cortex 0.18.1”.

Add it to your agent

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

Add ai-cortex mcp as an MCP server in your coding agent's settings, then use its tools from the agent.

What it does

  • Store typed project memories
    How to use it
    1. Connect your MCP client to ai-cortex mcp.
    2. Call the record_memory tool with worktreePath set to <your repo path>, type (for example decision), a title and a body.
    Tested
  • Index a git repository
    Not tested
  • Rank the files most relevant to a task
    Not tested
  • Search earlier agent sessions
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 1 of 4 features work
  4. Needs the network

Good for

  • index a git repo and rank relevant files for a task
  • search prior agent sessions for decisions and corrections
  • store and recall typed project memories like decisions and gotchas

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
  • Needed the network
  • Checked on 31 Oct 2026
  • Version 0.18.1

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

Differences the test machine hit

  • README: ai-cortex index /path/to/repo
    In the test: CLI index works; MCP index_project also requires `path` not `worktreePath` and is sensitive to cwd

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.