mcp-server-mysql
A Model Context Protocol server that provides read-only access to MySQL databases. This server enables LLMs to inspect database schemas and execute read-only queries.
Runssource: GitHubJavaScriptMITcommit b9c714e18242
JavaScript, MIT licensed.
mcp-server-mysql runs. An Argusic agent installed it in 15 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The @benborla29/mcp-server-mysql TypeScript project builds and passes all 215 tests against a real MySQL 8.0.36 server running from binary. The MCP server starts and responds to initialize, tools/list, and tools/call (mysql_query) requests over stdio transport, querying the live MySQL database and returning results.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Test failures: 10 tests failed - schema permissions tests expected write operations to be blocked but .env.test had all allow flags set to true, and multi-DB USE statement test failed due to missing multipleStatements config5 minutes
- MySQL server not installed and no root/sudo to install packages3 minutes
- MySQL server process was killed when parent shell exited (process group signal)2 minutes
- Node.js v18.19.1 does not meet minimum v20 requirement1 minute
- pnpm 12 required but not available1 minute
- Vitest config files (vitest.unit.config.ts, vitest.integration.config.ts, vitest.e2e.config.ts) referenced in package.json are missing from the repository1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- pnpm vitest run exited 0: 215 passed, 1 skipped across 16 test files. Also verified via MCP stdio protocol: tools/list and tools/call both returned proper responses with live query results (SELECT 42 AS answer returned [{answer:42}])
- Model tokens used
- 279,739
- Exact commit tested
- b9c714e18242
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "---" # Estimate - first commands ran around 22:28 echo "Start approx: 22:28" echo "Current: $(date +%H:%M)"' in /work/repo succeeded in 0ms: 2026-10-22 21:02:35 Start approx: 22:28 Current: 22:43 The uptime date is wrong (container started earlier than repo files). The wall clock from repo file… tokens used 279,739 The uptime date is wrong (container started earlier than repo files). The wall clock from repo file…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 15 minutes to install, slower than the median of the 14 comparable projects Argusic has measured.
Of the 15 JavaScript projects Argusic has installed and timed, mcp-server-mysql was the 13th fastest to reach a running state, and 10 of 15 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.20 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.19 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-server-mysql)Questions
- Does mcp-server-mysql run?
- Yes. mcp-server-mysql runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test mcp-server-mysql?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b9c714e18242. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mcp-server-mysql?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp-server-mysql take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcp-server-mysql need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp-server-mysql?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mcp-server-mysql compare with the alternatives?
- Of the 15 JavaScript projects Argusic has installed and timed, mcp-server-mysql was the 13th fastest to reach a running state, and 10 of 15 reached one at all.
- Where is the evidence for mcp-server-mysql?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.