pickfit

BrowseDeveloper CLIs

升目 masume

Keyboard-first terminal database client to browse, query and edit databases with AI chat.

Tested on Linux

Use it

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. install masume via npm globally

    npm install -g masume
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

npm install -g masume 2>&1
masume --version 2>&1
python3 -c "import sqlite3; con=sqlite3.connect('/home/sbx/work/notes.db'); cur=con.cursor(); cur.execute('DROP TABLE IF EXISTS notes'); cur.execute('CREATE TABLE notes(id INTEGER PRIMARY KEY, title TEXT, body TEXT)'); cur.executemany('INSERT INTO notes(title, body) VALUES (?,?)', [('hello','world'),('second','masume test')]); con.commit(); print(list(con.execute('SELECT * FROM notes')))"
mkdir -p /home/sbx/.config/masume && cat > /home/sbx/.config/masume/config.toml <<'EOF'
[mcp]
profiles = ["notes"]

[profile.notes]
engine = "sqlite"
database = "/home/sbx/work/notes.db"
mode = "read-only"
EOF
cat /home/sbx/.config/masume/config.toml
masume run ./notes.db -f csv 'select * from notes limit 100000' 2>&1

Check that it works

masume --version 2>&1

The output should contain “masume 0.0.17”.

First thing to try

python3 -c "import sqlite3; con=sqlite3.connect('$HOME/work/notes.db'); cur=con.cursor(); cur.execute('DROP TABLE IF EXISTS notes'); cur.execute('CREATE TABLE notes(id INTEGER PRIMARY KEY, title TEXT, body TEXT)'); cur.executemany('INSERT INTO notes(title, body) VALUES (?,?)', [('hello','world'),('second','masume test')]); con.commit(); print(list(con.execute('SELECT * FROM notes')))"
mkdir -p "$HOME"/.config/masume && cat > "$HOME"/.config/masume/config.toml <<'EOF'
[mcp]
profiles = ["notes"]

[profile.notes]
engine = "sqlite"
database = "$HOME/work/notes.db"
mode = "read-only"
EOF
cat "$HOME"/.config/masume/config.toml
masume run ./notes.db -f csv 'select * from notes limit 100000' 2>&1

Run masume run <database file> -f csv '<your SQL>' to query a database file from the terminal.

What it does

  • Browse and query databases
    How to use it
    1. Run masume run <database file> -f csv '<your SQL>' to run a query against a database file.
    2. Read the results printed as CSV rows.
    Tested
  • Chat with AI about the current connection
    Not tested
  • Share database profiles through an MCP server
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • browse database objects in the explorer
  • run SQL queries and keep history
  • export query results to CSV and JSON
  • compare schemas of two connections
  • serve database profiles to agents via MCP

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version masume 0.0.17

Differences the test machine hit

  • README: masume --mcp --check checks enabled MCP profiles
    In the test: create a config with [mcp] profiles=["notes"] and a [profile.notes] sqlite entry pointing at the db file; then it prints ok and exits 0

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.