Search for:
Why this server?
This server provides read-only access to MySQL databases, allowing inspection of database schemas, which directly addresses the need to determine the schema and relationships for website development.
Why this server?
An enhanced MCP server that enables LLMs to inspect database schemas with rich metadata and execute read-only SQL queries with safety checks. Relevant if the user ends up using PostgreSQL instead of MySQL.
Why this server?
MCP to access any database accessible via JDBC such as Postgres, Oracle, mysql, mariadb, sqlite etc. This offers more versatility for different SQL databases.
Why this server?
Visual Studio Code extension that allows you to manage many databases, including PostgreSQL, MySQL, SQL Server, DuckDB, Redis, MongoDB, and more. Offers the option to run an MCP server, providing access to those databases, their schemas, and the ability to execute queries.
Why this server?
Allows Cursor to interact with MySQL databases through the MCP protocol, enabling creation, querying, modification and deletion of database tables and records. Useful for setting up the database and schema.
Why this server?
Provides SQLAlchemy (via pyodbc) connectivity to any Database Management System (DBMS) that's accessible via SQLAlchemy.
Why this server?
A Model Context Protocol server that enables large language models to interact directly with Couchbase databases through natural language, supporting operations like querying buckets, performing CRUD operations, and executing N1QL queries.
Why this server?
A server that enables natural language interactions with Couchbase databases through the Model Context Protocol, allowing users to perform SQL++ queries on Couchbase Capella clusters using conversational commands.