$ loading_
Connect to relational databases for queries, schema inspection, and migrations.
This MCP tool is described as interacting with relational databases to run SQL, inspect schemas, and execute migrations. No secrets or remote endpoints are declared and the source is available, so no clear high-risk red flags are evident; however, it still warrants caution due to local code execution and direct database data operations. Trust is moderated by third-party registry distribution, low adoption, and unclear maintenance.
The materials explicitly state there are no required secrets or environment variables, and no API keys, tokens, or other sensitive credentials are declared. However, if it connects to protected databases in practice, database credentials may still need to be configured at runtime, which is not documented here.
No fixed remote endpoint is declared, but the stated functionality includes interacting with PostgreSQL/MySQL and similar databases, which implies queries and data may be sent to user-specified database hosts. This is normal for a database tool, and there is no evidence of exfiltration to unrelated or unknown third-party endpoints.
The system flags that it executes code; combined with the description of running SQL queries and executing migrations, it likely runs local service logic and can trigger database changes. This kind of local execution is typical for an MCP tool, and the provided materials show no sign of unusually broad system permission requests.
The tool can query databases, inspect schemas, and execute migrations, so its data access scope includes the structure and contents of any connected database and may allow writes or destructive changes. This scope is consistent with its stated purpose, and the materials do not indicate excessive filesystem access beyond the database use case.
An open-source repository exists, making the code theoretically auditable and reducing risk. However, it comes from a third-party registry, has no declared license, 0 GitHub stars, unknown maintenance status, and no README, which limits verifiability and community trust; the implementation and dependencies should be reviewed before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-server-database" yet — see the docs or source repo.
Connect to my PostgreSQL database, list all tables, column types, primary keys, and foreign key relationships, then summarize the core business entities.
A database schema overview with tables, columns, relationships, and a summary of key business entities.
Query the SQLite database for daily order counts and revenue over the last 30 days, and return the results sorted by date ascending.
A query result table for analysis, including date, order count, and revenue.
Run this set of migration scripts on the MySQL database and verify whether the new tables and indexes were created successfully; explain any failures.
Migration execution results including success status, change summary, and explanations for any errors.
Query and manage multiple databases with read-only access and schema inspection.
Connect to major databases via MCP to run SQL queries and commands.
Connect to PostgreSQL via MCP for queries, schema inspection, and database changes.
Connect to multiple databases to query, inspect schemas, and access remotely via SSH.
Connect to PostgreSQL and MySQL, run SQL, and manage database transactions.
Operate PostgreSQL, MySQL, and SQLite databases with natural language.