pickfit

BrowseMCP servers

Distillery

Team knowledge base that captures working-session notes and surfaces them via conversational search.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.11+
  • System packages: uv
  1. install distillery-mcp with fastembed via uv tool

    uv tool install 'distillery-mcp[fastembed]>=0.6.0'
Where the README and reality differ
  • README: example entry_type 'decision' in /distill docs
    What worked: distillery_store only accepts bookmark, digest, feed, github, idea, inbox, meeting, minutes, person, project, reference, session – use 'idea' or 'session'

Add it to your agent

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

Add distillery-mcp as a server in your MCP client, then call its tools such as distillery_store and distillery_search.

What it does

  • Capture, classify, connect and surface team knowledge
    How to use it
    1. Call the distillery_store tool with your note as content, plus an entry_type (such as idea) and an author.
    2. Check the tool's text reply to confirm the entry was stored.
    Tested
  • Search team knowledge by meaning
    How to use it
    1. Call the distillery_search tool with a query describing what you are looking for.
    2. Read the matching entries in the tool's text reply.
    Tested
  • Capture session knowledge with duplicate detection
    Not shown working
  • Combine several entries into a summary with citations
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • capture session knowledge with dedup detection
  • semantic search entries with provenance
  • store URLs with auto-generated summaries
  • record meeting notes with updates
  • sync GitHub issues and PRs into knowledge base

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 31 Oct 2026
  • Version 0.7.0

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

Differences the test machine hit

  • README: distillery-mcp --version
    In the test: --version flag not supported; use --help

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.