pickfit

BrowseMCP servers

Database MCP

Single-binary MCP server connecting AI assistants to MySQL, PostgreSQL, and SQLite.

Tested on Linux

Use it

Linux x86_64

  1. download install script

    curl -fsSL https://dbmcp.haymon.ai/install.sh -o /tmp/install.sh
  2. install dbmcp binary via install.sh

    bash /tmp/install.sh
Where the README and reality differ
  • README: launch command `dbmcp`
    What worked: must use subcommand `dbmcp stdio` with required --db-backend and --db-name args; bare `dbmcp` exits with usage

Check that it works

dbmcp --version 2>&1

The output should contain “dbmcp 0.15.2”.

Add it to your agent

claude mcp add dbmcp -- dbmcp stdio --db-backend sqlite --db-name '<db-name>'
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "dbmcp": {
      "command": "dbmcp",
      "args": [
        "stdio",
        "--db-backend",
        "sqlite",
        "--db-name",
        "<db-name>"
      ]
    }
  }
}

Replace <db-name> with your own path.

Start the server for your MCP client with dbmcp stdio --db-backend sqlite --db-name <database file>.

What it does

  • Connect an AI assistant to a SQL database
    How to use it
    1. Add dbmcp stdio --db-backend sqlite --db-name <database file> as a server in your MCP client.
    2. Ask the assistant to run a query; it uses the readQuery tool.
    Tested
  • Explore database structure with MCP tools
    How to use it
    1. Start the server with dbmcp stdio --db-backend sqlite --db-name <database file>.
    2. Ask the assistant to list tables; it calls the listTables tool.
    Tested
  • Hide personal data in query results
    How to use it
    1. Start the server with dbmcp stdio --db-backend sqlite --db-name <database file> --pii true.
    2. Run queries through readQuery as usual.
    Tested
  • Block writes with read-only mode
    Not tested

How far pickfit got

Linux x86_64

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

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

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.15.2

An MCP client handshake over stdio listed 5 tools, and a call to listTables 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.