Why this server?
Supports querying MySQL databases along with PostgreSQL.
Why this server?
Provides read-only access to MySQL databases, enabling schema inspection and read-only query execution.
Why this server?
Enables Cursor to interact with MySQL databases through the MCP protocol, supporting data manipulation and schema management.
Why this server?
Provides read-only access to MySQL databases, enabling LLMs to inspect database schemas and execute read-only queries.
Why this server?
This server enables AI models to interact with MySQL databases through a standardized interface.
Why this server?
Added support for STDIO mode and SSE mode, multiple SQL execution, querying database table names and fields based on table comments, SQL Execution Plan Analysis and Chinese field to pinyin conversion
Why this server?
Enhances LLMs to inspect database schemas with rich metadata and execute read-only SQL queries with safety checks (Could be helpful if needing to migrate from MySQL to Postgres)
Why this server?
A Model Context Protocol (MCP) server implementation for connecting to and working with various database systems.
Why this server?
MCP to access any database accessible via JDBC such as Postgres, Oracle, mysql, mariadb, sqlite etc.