Loading...
{
"mcpServers": {
"stdio-db-mcp-server": {
"command": "/path/to/db-mcp-server/server",
"args": ["-t", "stdio", "-c", "/path/to/config.json"]
}
}
}query_<db_id>Executes SELECT queries and returns results as a tabular dataset.
Read-only operation, no data modification.
execute_<db_id>Runs data manipulation statements (INSERT, UPDATE, DELETE).
Modifies database content, potential for data loss or corruption.
transaction_<db_id>Manages database transactions (BEGIN, COMMIT, ROLLBACK).
Improper transaction handling can lead to data inconsistency.
schema_<db_id>Retrieves information about database schema (tables, columns, indexes).
Read-only operation, no data modification.
performance_<db_id>Analyzes query performance and provides optimization suggestions.
Read-only operation, no data modification.
create_hypertable_<db_id>Converts a standard table to a TimescaleDB hypertable.
Modifies database schema, potential for data loss if not handled correctly.
time_series_query_<db_id>Executes optimized time-series queries with bucketing.
Read-only operation, no data modification.
The DB MCP Server offers a convenient way to interact with multiple databases, but it's crucial to secure the configuration file and implement robust input validation to prevent SQL injection attacks. Using read-only connections where possible significantly reduces risk. The server's safety depends heavily on the security practices of the user and the AI agent interacting with it.