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.
Runs with mockssource: GitHubJavaScriptMITcommit b9c714e18242
JavaScript, MIT licensed.
mcp-server-mysql runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
151 unit tests pass; MCP server launches in both stdio and remote HTTP modes, responding to initialize requests with proper capabilities.
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 92 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.
- dotenv.config() loaded .env before vitest stubs, breaking env-override in 3 unit tests5 minutes
- Fatal safeExit(1) on DB connection test failure killed remote HTTP server at startup5 minutes
- executeReadOnlyQuery test didn't expect new timing entry in response3 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx vitest run tests/unit/ exited 0, 151 passed; node dist/index.js --stdio responded to MCP initialize; IS_REMOTE_MCP=true + curl POST /mcp returned HTTP 200 with valid MCP response
- Model tokens used
- 205,154
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Fix**: Updated `tests/unit/query.test.ts` to assert the timing entry separately.
**Verification**:
- `npx vitest run tests/unit/` — **151 passed** across 8 test files
- `node dist/index.js --stdio` with MCP init request — returns proper capabilities JSON
- `IS_REMOTE_MCP=true REMOTE_SECRET_KEY=test123 PORT=3480 node dist/index.js` + `curl POST /mcp` — …
**What couldn't be verified**: Integration tests require MySQL 5.7+/8.0+ running on `127.0.0.1:3306…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [{"msg": "dot…
tokens used
205,154Replay 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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 2 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 10 JavaScript projects Argusic has installed and timed, mcp-server-mysql was the 7th fastest to reach a running state, and 5 of 10 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| 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?
- mcp-server-mysql runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 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. One attempt is 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.19: 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?
- 2 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?
- 3 things broke in the recorded run, and 3 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 10 JavaScript projects Argusic has installed and timed, mcp-server-mysql was the 7th fastest to reach a running state, and 5 of 10 reached one at all.
- Where is the evidence for mcp-server-mysql?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.