pickfit

BrowseDeveloper CLIs

agent-database-cli

Local CLI that lets agents connect, query, and inspect MySQL, Postgres, Redis, Oracle, MongoDB.

Tested on Linux and WindowsKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • crates:hickory-proto 0.25.2 hickory-proto: NSEC3 closest-encloser proof validation enters unbounded loop on cross-zone responses (GHSA-3v94-mw7p-v465, high, no fix yet)
  • crates:hickory-resolver 0.25.2 hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures (GHSA-5j98-2g5x-46v6, high, fixed in 0.26.2)
See 8 more

Linux x86_64

You need first

  • Runtimes: Node.js >=20
  • Needs the network
  1. Install via npm global

    npm install -g agent-database-cli

Check that it works

agent-database-cli --help 2>&1

The output should contain “Usage: agent-database-cli”.

First thing to try

agent-database-cli list 2>&1

Run agent-database-cli list to see the supported database types and your configured connections.

Windows x86_64

You need first

  • Runtimes: Node.js >=20
  • Needs the network
  1. npm install -g agent-database-cli

    npm install -g agent-database-cli
Where the README and reality differ
  • README: agent-database-cli list --format json / 默认格式
    What worked: global --format must be before subcommand (agent-database-cli --format json list); default list already outputs json without flag

Check that it works

$env:Path = [Environment]::GetEnvironmentVariable('Path','Machine') + ';' + [Environment]::GetEnvironmentVariable('Path','User'); agent-database-cli --help

The output should contain “list 展示支持的数据库类型和本地连接”.

First thing to try

agent-database-cli install-skill --dry-run

Run agent-database-cli list to see the supported database types and your configured connections.

What it does

  • List supported database types and connections
    How to use it
    1. Add your connections to config.json in the .agent-database-cli folder in your home directory.
    2. Run agent-database-cli list to see the supported types and your configured connections.
    Tested
  • Run SQL, Redis and MongoDB commands
    Not shown working
  • Inspect database metadata such as tables and columns
    Not tested
  • Edit the configuration in a local page
    Not shown working

How far pickfit got

Linux x86_64

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

Windows x86_64

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

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • list supported database types and configured connections
  • execute SQL, Redis commands, or MongoDB JSON commands
  • inspect database metadata such as tables, columns, and collections
  • enforce per-connection read-only mode and command blacklist
  • edit connections visually in a local page with validation

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 0.4.1

Differences the test machine hit

  • README: README grep shows only list/editor/install-skill command lines, no exec/meta example lines
    In the test: exec/meta syntax discovered via exec --help / meta --help: exec --db <DB> --command <COMMAND>, meta --db <DB> --type tables|columns|collections|keys
  • README: README badge shows release v0.4.0
    In the test: installed version is 0.4.1 (seen in editor health)

Windows x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.4.1

Differences the test machine hit

  • README: config at ~/.agent-database-cli/config.json auto-created
    In the test: directory ~/.agent-database-cli not auto-created, mkdir -Force needed before writing config.json
  • README: (Windows steps)
    In the test: pickfit ran these steps in PowerShell 7 (pwsh 7.6.9) as a standard user; the built-in Windows PowerShell 5.1 is not verified and does not run `&&`.
  • README: (Windows steps)
    In the test: On Windows, open a new terminal after installing so PATH includes the tool; the sandbox refreshed PATH in the same session instead.

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.