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 universal interface that enables AI Agents to communicate with Hologres databases, allowing them to retrieve database metadata and execute SQL operations.
Why this server?
Enables IDE access to Supabase databases with SQL query execution, schema management, Auth admin operations, and built-in safety controls to prevent accidental destructive actions.
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 Model Context Protocol server that enables LLMs to understand BigQuery dataset structures and execute SQL queries.
Why this server?
A Model Context Protocol server implementation that enables AI assistants to securely interact with GreptimeDB, allowing them to explore database schema, read data, and execute SQL queries through a controlled interface.
Why this server?
A Model Context Protocol server that enables secure interaction with Microsoft SQL Server databases, allowing AI assistants to list tables, read data, and execute SQL queries through a controlled interface.
Why this server?
Universal database MCP server connecting to MySQL, PostgreSQL, SQLite, DuckDB and etc.
Why this server?
A Model Context Protocol server that provides access to BigQuery. This server enables LLMs to inspect database schemas and execute queries.