execute_query
Execute SQL query on a specific database connection
LABSCO SUMMARY
Every call is scoped to a connection configured outside this server, so what it can reach is decided before it starts.
The surface is deliberately small — execute_query with parameters kept apart from query, plus the calls needed to see what you are connected to and bring a dead connection back without a restart of your own. list_connections deserves a second look for its include_credentials flag: the connection inventory can be returned with stored credentials inside it, so that flag decides what ends up in the model's context. Which engines a connection can speak to is a property of the configuration this server reads, and the tool surface itself takes no position on it.
What it is
A SQL front end over pre-configured database connections, exposing query execution with bound parameters, database listing, connection status and a retry for connections that failed.
What you get
- execute_query runs a query against a named connection, keeping parameters separate from the query text and taking database to choose which one inside that connection to run against.
- list_databases returns the databases visible on a given connection_name, or across every configured connection when it is left out.
- list_connections returns each configured connection with detailed information and its status, and takes include_credentials to decide whether stored credentials come back in the response.
- retry_failed_connections re-attempts a connection that did not come up, by connection_name.
Requirements
At least one database connection already configured for the server: execute_query, list_databases and retry_failed_connections each take a connection_name, and list_connections reports what is configured.
Setup effort
One command — npx -y @ahmetbarut/mcp-database-server
USE CASES
01
Answering a question that needs the real data behind it
Find which databases the connection exposes, then run the query with values bound as parameters rather than pasted into the SQL.
02
Working out why a query stopped returning anything
Check the status the server holds for each connection, then re-attempt the one that dropped instead of restarting everything.
03
Getting your bearings in a set of connections somebody else configured
Read the inventory of connections and then walk the databases behind each one before writing any SQL.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_connections
List all database connections with detailed information and status
list_databases
List databases from a specific connection or all configured connections
retry_failed_connections
Retry failed database connections
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
- npx on PATH
- Node.js v23
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-database-server": {
"command": "npx",
"args": [
"-y",
"@ahmetbarut/mcp-database-server"
]
}
}
}npx
TERMINAL
npx -y @ahmetbarut/mcp-database-server
