Search for:
Why this server?
Allows AI assistants to list tables, read data, and execute SQL queries through a controlled interface, making database exploration and analysis safer and more structured.
Why this server?
Enables interaction with a MySQL database via JSON commands, supporting read-only queries, test execution of write queries, and table information retrieval through Docker.
Why this server?
A Model Context Protocol server that provides read-only access to MySQL databases, enabling LLMs to inspect database schemas and execute read-only queries.
Why this server?
A natural language interface that allows Claude to execute SQL queries on your local MySQL databases, enabling database interaction using natural language.
Why this server?
A server that enables AI models to interact with MySQL databases through a Model Control Protocol, providing tools for table creation, schema inspection, query execution, and data retrieval.
Why this server?
A Model Context Protocol server that enables SQL query execution, database management, and business intelligence capabilities through MySQL connections.
Why this server?
Universal database MCP server connecting to MySQL, PostgreSQL, SQLite, DuckDB and etc.
Why this server?
An implementation of the Model Context Protocol that enables interaction with ArangoDB databases, allowing users to perform queries, list databases and collections through natural language.
Why this server?
A server implementing the Model Context Protocol (MCP) for Cursor that allows using a PostgreSQL database as storage for model contexts, enabling secure database exploration and querying.
Why this server?
An MCP server that provides read-only access to MySQL databases.