Search for:
Why this server?
This server works with both Supabase projects (which use PostgREST) and standalone PostgREST servers.
Why this server?
Enables Cursor and Windsurf to safely interact with Supabase databases by providing tools for database management, SQL query execution, and Supabase Management API access with built-in safety controls.
Why this server?
A Model Context Protocol server implementation for PostgreSQL databases, enabling SQL queries, database operations, and schema management through MCP.
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.
Why this server?
Connects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through MCP Clients like Claude Desktop and Cursor.
Why this server?
An MCP server that enables graph database interactions with Neo4j, allowing users to access and manipulate graph data through natural language commands.
Why this server?
A server based on Model Context Protocol that enables AI models to interact with MySQL databases through a standardized interface, supporting features like query execution, table listing, and automated connection management.
Why this server?
Enables interaction with Azure Table Storage directly through Cline. This tool allows you to query and manage data in Azure Storage Tables.
Why this server?
An MCP server that enables access to Azure Data Explorer (ADX) clusters, allowing users to list tables, execute queries, and retrieve schema information.