Search for:
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 universal interface that enables AI Agents to communicate with Hologres databases, allowing them to retrieve database metadata and execute SQL operations.
Why this server?
A Model Context Protocol server that enables LLMs to understand BigQuery dataset structures and execute SQL queries.
Why this server?
Enables LLMs to perform statistical analysis and generate ML predictions on user data from databases or CSV files through a Model Context Protocol server.
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?
This is an MCP server for PostgREST. It allows LLMs perform database queries and operations on Postgres databases via PostgREST.
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?
Connects to CockroachDB instances and exposes database structures as resources, enabling SQL query execution and analysis through Claude's interface.
Why this server?
Integrates with Google Drive to enable listing, searching, and reading files, plus reading and writing to Google Sheets.