Search for:
Why this server?
This server provides read-only access to MySQL databases, enabling LLMs to inspect database schemas and execute read-only queries. While it doesn't explicitly mention socket connections, it provides the core functionality of running MySQL queries.
Why this server?
This server enables AI models to interact with MySQL databases through a standardized interface, suggesting it can handle running 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. Does not explicitly mention socket connections but enables running queries.
Why this server?
A TypeScript-based MCP server that facilitates SQL query execution and MySQL database connectivity using environment variables, which could include socket configurations.
Why this server?
This server helps with providing LSP functionality, a tool that can be used for assisting database interactions.
Why this server?
Provides generic Open Database Connectivity (ODBC) to any Database Management System (DBMS) that's accessible via an ODBC Connector (Driver), and can be used to run sql queries. Although not a direct mysql socket, it may use it under the hood
Why this server?
A Model Context Protocol server that enables AI agents to execute SQL queries against a MySQL database, supporting operations like reading data, creating tables, inserting, updating, and deleting records.
Why this server?
An enhanced Model Context Protocol server that enables LLMs to inspect database schemas with rich metadata and execute read-only queries with safety checks. This provides more in-depth features that could assist in running queries
Why this server?
Provides SQLAlchemy (via pyodbc) connectivity to any Database Management System (DBMS) that's accessible via SQLAlchemy, and can be used to run sql queries. Although not a direct mysql socket, it may use it under the hood
Why this server?
Provides access to airtable bases for querying via SQL