MySQL MCP Server vs MCP Debug Recorder
MySQL MCP Server is an MCP server published by musaddiq-dev. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Debug Recorder is an MCP server published by oaslananka. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MySQL MCP Server |  MCP Debug Recorder |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (PyPI): 103 Downloads/week (PyPI): 46 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.3 Downloads/month (npm): 231 Downloads/week (npm): 21 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | MySQL MCP Server | MCP Debug Recorder |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mdev-mysql-mcp-server) | On your machine (debug-recorder-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | 11, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/musaddiq-dev/mysql-mcp-server | github.com/oaslananka/debug-recorder-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
MySQL MCP Server
Python MCP server for MySQL database inspection and querying
MCP Debug Recorder
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
How to run each
MySQL MCP Server As a local MCP server: PyPI package
claude mcp add --env "MYSQL_DATABASE=<YOUR_MYSQL_DATABASE>" --env "MYSQL_PASSWORD=<YOUR_MYSQL_PASSWORD>" --transport stdio mysql-mcp-server -- uvx mdev-mysql-mcp-serverRequires: MYSQL_DATABASE, MYSQL_PASSWORD (secret)
MCP Debug Recorder As a local MCP server: npm package
claude mcp add --env "DEBUG_RECORDER_HTTP_TOKEN=<YOUR_DEBUG_RECORDER_HTTP_TOKEN>" --transport stdio debug-recorder-mcp -- npx -y debug-recorder-mcpRequires: DEBUG_RECORDER_HTTP_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only MySQL MCP Server asks for
MYSQL_DATABASEMYSQL_HOSTMYSQL_PASSWORD (secret)MYSQL_POOL_SIZEMYSQL_PORTMYSQL_READ_QUERY_LIMITMYSQL_USER
Only MCP Debug Recorder asks for
DEBUG_RECORDER_ALLOWED_HOSTSDEBUG_RECORDER_ALLOWED_ORIGINSDEBUG_RECORDER_DBDEBUG_RECORDER_HTTP_TOKEN (secret)DEBUG_RECORDER_MAX_BODY_BYTESDEBUG_RECORDER_REDACT_BEFORE_STOREDEBUG_RECORDER_REMOTE_HTTPFUZZY_THRESHOLDHOSTPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: MySQL MCP Server · What it can do: MCP Debug Recorder · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.