| name | whodb |
| description | Query and explore databases via MCP. Use when the user asks to inspect schemas, run SQL, browse tables, analyze data quality, generate ER diagrams, or work with PostgreSQL, MySQL, MariaDB, TiDB, SQLite, MongoDB, Redis, ClickHouse, Elasticsearch, or DuckDB. |
| license | Apache-2.0 |
| metadata | {"author":"clidey","version":"0.106.0"} |
| compatibility | Requires Node.js (npx) or the whodb-cli binary installed. |
WhoDB
Query databases, explore schemas, analyze data quality, and get optimization recommendations through the WhoDB MCP server.
Setup
If the WhoDB MCP server is not connected, set it up:
-
Add the MCP server (npx, no install needed):
codex mcp add whodb -- npx -y @clidey/whodb-cli mcp serve
-
Or if whodb-cli is installed locally:
codex mcp add whodb -- whodb-cli mcp serve
-
Configure database connections via environment variables:
export WHODB_POSTGRES='[{"alias":"prod","host":"localhost","user":"user","password":"pass","database":"mydb","port":"5432"}]'
export WHODB_MYSQL_1='{"alias":"dev","host":"localhost","user":"user","password":"pass","database":"devdb","port":"3306"}'
After adding the MCP server, restart Codex.
Available MCP Tools
whodb_connections
List all available database connections.
No parameters required.
Returns: connection names with type and source (env/saved).
whodb_schemas
List schemas in a database.
Parameters:
- connection: Connection name (optional if only one exists)
whodb_tables
List tables in a schema.
Parameters:
- connection: Connection name (optional)
- schema: Schema name (optional, uses default)
whodb_columns
Describe table columns and types.
Parameters:
- connection: Connection name (optional)
- table: Table name (required)
- schema: Schema name (optional)
whodb_query
Execute SQL queries with security validation.
Parameters:
- connection: Connection name (optional)
- query: SQL query to execute
whodb_explain
Run EXPLAIN for a SQL query.
Parameters:
- connection: Connection name (optional)
- query: SQL query to analyze
whodb_erd
Load graph/relationship metadata for ER diagrams.
Parameters:
- connection: Connection name (optional)
- schema: Schema name (optional)
whodb_diff
Compare schema metadata between two connections.
Parameters:
- source: Source connection name (required)
- target: Target connection name (required)
whodb_audit
Run data quality audits on a table.
Parameters:
- connection: Connection name (optional)
- table: Table name (required)
- schema: Schema name (optional)
whodb_suggestions
Load backend-generated query suggestions for a connection.
Parameters:
- connection: Connection name (optional)
- schema: Schema name (optional)
whodb_confirm
Confirm a pending write operation (only available in confirm-writes mode, which is the default).
Parameters:
- token: Confirmation token from a pending write
whodb_pending
List pending confirmation tokens.
No parameters required.
Standard Workflow
Step 1: Discover connections
whodb_connections → list available databases
Step 2: Explore schema
whodb_schemas(connection="name") → list schemas
whodb_tables(connection="name", schema="public") → list tables
whodb_columns(connection="name", table="users") → column details
Step 3: Query data
whodb_query(connection="name", query="SELECT * FROM users LIMIT 10")
Step 4: Analyze (as needed)
whodb_explain(connection="name", query="SELECT ...") → query plan
whodb_erd(connection="name") → table relationships
whodb_audit(connection="name", table="users") → data quality
whodb_diff(source="prod", target="staging") → schema comparison
Query Building
When converting natural language to SQL:
- Always check schema first with
whodb_tables and whodb_columns
- Match entities to table names, attributes to column names
- Identify foreign key joins from column metadata
- Use LIMIT for exploratory queries (default: 100)
Date handling varies by database
| Intent | PostgreSQL | MySQL | SQLite |
|---|
| Last 7 days | >= NOW() - INTERVAL '7 days' | >= DATE_SUB(NOW(), INTERVAL 7 DAY) | >= DATE('now', '-7 days') |
| Start of month | >= DATE_TRUNC('month', CURRENT_DATE) | >= DATE_FORMAT(NOW(), '%Y-%m-01') | >= DATE('now', 'start of month') |
Security Modes
The MCP server defaults to confirm-writes mode (writes require confirmation via whodb_confirm).
--read-only: blocks all write operations--safe-mode: read-only + strict security validation--allow-write: full write access without confirmation
Safety Rules
- Always explore schema before writing queries
- Use LIMIT for exploratory queries
- Prefer specific columns over SELECT *
- Never generate DELETE, UPDATE, or DROP unless explicitly requested
- Never expose or log credentials
- Use connection names, not connection strings
