Loading...

Back to Database

Legion

VERIFIED

Legion

Safety: 50/100

0.0(0)

Database MCP provides a unified interface to query and manage multiple databases via the Model Context Protocol, enabling AI assistants to interact with data.

MCP ServersData & DatabasesAI & LLMDevelopmentSearch & WebCommunicationUtilitiesFreemium

Boost this tool

Subscribe to listing upgrades or segmented pushes.

Log in to purchase

Overview

Database MCP provides a unified interface to query and manage multiple databases via the Model Context Protocol, enabling AI assistants to interact with data.

Database MCP offers a convenient way to access databases, but the ability to execute arbitrary SQL queries presents a significant risk. It is safe when used with read-only databases and carefully constructed queries. It is risky when used with write-enabled databases and untrusted queries.

Performance depends on the complexity of the SQL queries and the performance of the underlying databases. Consider optimizing queries and using database indexes to improve performance.

Cost depends on the resources used by the databases and the MCP server. Consider the cost of database hosting, network bandwidth, and server resources.

Python85 starsGPL-3.0Released 5/10/2025

Connections & Capabilities

Connects To

GitHubPostgreSQLMySQLSQLite

Capabilities

ReadWriteExec

Client Compatibility

Claude Desktop

full

Cursor

untested

Windsurf

untested

VS Code (Copilot)

untested

Quickstart

Install

pip install database-mcp

Claude Desktop Config

{
    "mcpServers": {
      "database-mcp": {
        "command": "uvx",
        "args": [
          "database-mcp"
        ],
        "env": {
          "DB_CONFIGS": "[{\"id\":\"pg_main\",\"db_type\":\"pg\",\"configuration\":{\"host\":\"localhost\",\"port\":5432,\"user\":\"user\",\"password\":\"pw\",\"dbname\":\"postgres\"},\"description\":\"PostgreSQL Database\"},{\"id\":\"mysql_data\",\"db_type\":\"mysql\",\"configuration\":{\"host\":\"localhost\",\"port\":3306,\"user\":\"root\",\"password\":\"pass\",\"database\":\"mysql\"},\"description\":\"MySQL Database\"}]"
        },
        "disabled": true,
        "autoApprove": []
      }
    }
}

Environment Variables

DB_TYPEDB_CONFIGDB_CONFIGS

Tools (10)

high

execute_query

Executes a SQL query against the database and returns the results as a markdown table.

Allows arbitrary SQL execution, potentially leading to data modification or deletion.

high

execute_query_json

Executes a SQL query and returns results as JSON.

Allows arbitrary SQL execution, potentially leading to data modification or deletion.

safe

get_table_columns

Retrieves the column names for a specified table.

Read-only operation, no side effects.

safe

get_table_types

Retrieves the column types for a specified table.

Read-only operation, no side effects.

safe

get_query_history

Retrieves the recent query history.

Read-only operation, no side effects.

safe

list_databases

Lists all available database connections.

Read-only operation, no side effects.

safe

get_database_info

Retrieves detailed information about a database, including its schema.

Read-only operation, no side effects.

safe

find_table

Finds which database contains a specific table.

Read-only operation, no side effects.

safe

describe_table

Retrieves a detailed description of a table, including column names and types.

Read-only operation, no side effects.

safe

get_table_sample

Retrieves a sample of data from a table.

Read-only operation, no side effects.

Security

Auth Method

Environment Variable

Known Risks

!SQL injection vulnerabilities due to direct SQL query execution.
!Exposure of sensitive database credentials if environment variables are not properly secured.
!Potential for data breaches if database permissions are not correctly configured.
!Lack of input validation can lead to unexpected errors or malicious behavior.
!Unintended data modification or deletion through `execute_query` tool.

Safety Score

50

moderate risk

Database MCP offers a convenient way to access databases, but the ability to execute arbitrary SQL queries presents a significant risk. It is safe when used with read-only databases and carefully constructed queries. It is risky when used with write-enabled databases and untrusted queries.

Positive

+Database access is mediated through the Legion Query Runner, providing a degree of abstraction.
+MCP integration allows for controlled exposure of database operations to AI assistants.
+Secure credential management aims to separate credentials from application code.
+Multi-database configurations allow for isolation of sensitive data.

Risks

-Direct SQL query execution can lead to SQL injection vulnerabilities if not properly sanitized.
-Lack of explicit RBAC means access control relies on the underlying database permissions.
-Improperly configured database connections can expose sensitive data.
-The `execute_query` tool allows arbitrary SQL execution, which can be destructive.

Use Cases

Data Analysis

-Generating reports from multiple databases.
-Analyzing customer behavior across different data sources.
-Identifying trends and patterns in sales data.

AI Assistant Integration

-Enabling AI assistants to answer questions about data stored in databases.
-Automating data entry and retrieval tasks.
-Providing AI-powered insights based on database content.

Database Management

-Monitoring database performance.
-Auditing database access.
-Simplifying database administration tasks.

Application Development

-Building data-driven applications that access multiple databases.
-Creating APIs for accessing database data.
-Integrating databases with other systems.

Who Is This For?

Best For

Data analysts who need to query multiple databases.
AI developers who want to integrate databases with AI assistants.
Database administrators who need to manage multiple databases.
Application developers building data-driven applications.

Not Ideal For

Environments with strict security requirements and no SQL injection protection.
Applications that require real-time data access with low latency.
Scenarios where database credentials cannot be securely stored.

Autonomy & Execution

Default ModeConfigurable

Destructive Tools

Autonomy depends on the configured database permissions and the queries executed. Exercise caution when granting autonomous access to write-enabled databases.

StatelessYes

Retry LogicNot documented

ConcurrencySingle-threaded

Production Tip

Monitor database performance and resource usage to ensure optimal performance and prevent bottlenecks.

FAQ

What databases are supported?

PostgreSQL, MySQL, SQL Server, and other databases supported by Legion Query Runner.

How do I configure the database connections?

Using environment variables or command-line arguments with JSON configuration.

How do I specify which database to use for a query?

Use the `db_id` parameter with the database-specific tools.

Is there support for schema discovery?

Yes, the server automatically discovers and exposes database schemas.

How do I secure my database credentials?

Store credentials securely using environment variables and restrict access to the server.

Can I use this with LangChain?

Yes, the server is designed to work with AI development environments like LangChain.

What is the Model Context Protocol (MCP)?

MCP is a specification for maintaining context in AI applications, used here to expose database operations as tools.

Key Features

Data & Databases AI & LLM Development Search & Web Communication Utilities

Unified Query Runner - Provides a consistent interface for executing queries across multiple database systems.

Model Context Protocol Integration - Standardizes communication between AI agents and data stores for seamless interoperability.

Python-based Implementation - Allows for easy integration into existing Python-based AI agent frameworks and workflows.

Multi-Database Support - Enables interaction with various database types through a single unified protocol.

Use Cases & Problems Solved

Use Cases

•Use when you need to grant an AI assistant direct read and write access to your SQL or NoSQL databases using the Model Context Protocol.
•Perfect for building automated data reporting pipelines where an AI needs to query live database records to generate summaries.
•Ideal if you need to provide LLMs with a structured, standardized way to execute complex queries across multiple heterogeneous database systems.
•Great for developers building internal AI-powered data exploration tools that require secure, protocol-based database interactions.
•Use when you want to enable natural language querying of production databases without writing custom API endpoints for every single query requirement.

Problems Solved

✓Eliminates the need to manually bridge the gap between AI models and database schemas by providing a standardized MCP interface.
✓Reduces the engineering overhead required to build custom connectors for every new database type an AI assistant needs to access.
✓Solves the issue of disjointed data access patterns by providing a unified query runner for diverse database environments.
✓Removes the friction of writing repetitive boilerplate code for database authentication and query execution within AI agent workflows.

Who It's For

Python backend developers building AI-integrated enterprise applications.AI infrastructure engineers designing standardized data access layers for agentic systems.Data platform engineers managing multi-database environments for internal tool development.LLM application developers working on RAG pipelines that require live database state context.

Metrics

Discovered2/14/2026

Reviews0

Saved By0 users

Related Tools

Legion | AI Builder Hub Review & Alternatives | Flaex AI