Read-only SQL MCP server for PostgreSQL and MySQL.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"sql-query-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# sql-query-mcp [中文版](README-zh.md) A general-purpose MCP server that lets AI work with multiple databases within clear boundaries. [](https://glama.ai/mcp/servers/andyWang1688/sql-query-mcp) ## Current database support | Database | Status | Current availability | | --- | --- | --- | | PostgreSQL | Supported | Available today | | MySQL | Supported | Available today | | Hive | Supported | Available today | | SQLite | Candidate | Not supported yet | | SQL Server | Candidate | Not supported yet | | ClickHouse | Candidate | Not supported yet | ## Product value `sql-query-mcp` helps AI clients discover schema, sample data, and analyze read-only queries through one controlled MCP interface. It keeps connection handling, namespace rules, SQL validation, and audit logging on the server side, so you can expose useful database context to AI without exposing raw connection strings or flattening engine-specific concepts. ## What AI can do with it The current tool set focuses on database discovery, controlled query workflows, asynchronous read-only queries, batched query result exports, and one narrow local file import path. You can use it to help an AI assistant understand structure before it generates SQL, runs a bounded query, starts a long-running read-only query, exports PostgreSQL or MySQL results to a local file, or imports a prepared CSV/XLSX file into an existing table. MySQL and Hive support `explain_query`. Hive uses `EXPLAIN` and `EXPLAIN ANALYZE` for `explain_query`. | Tool | PostgreSQL | MySQL | Hive | Purpose | | --- | --- | --- | --- | --- | | `list_connections()` | Yes | Yes | Yes | List configured connections | | `list_schemas(connection_id)` | Yes | No | No | List visible PostgreSQL schemas | | `list_databases(connection_id)` | No | Yes | Yes | List visible MySQL or Hive databases | | `list_tables(connection_id, schema?, database?)` | Yes | Yes | Ye…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.