Search for:
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, which is directly relevant to the user's request to connect and read/write to their Supabase database.
Why this server?
This server works with both Supabase projects (which use PostgREST) and standalone PostgREST servers. This allows LLMs perform database queries and operations on Postgres databases.
Why this server?
A TypeScript-based server that enables language models to securely query PostgreSQL databases, including those behind SSH bastion tunnels. Supabase uses PostgreSQL.
Why this server?
An MCP server that enables natural language querying of Supabase PostgreSQL databases using Claude 3.7, allowing users to inspect schemas, execute SQL, manage migrations, and convert natural language to SQL queries.
Why this server?
A Model Context Protocol (MCP) server that enables LLMs to interact directly with MongoDB databases, allowing them to query collections, inspect schemas, and manage data seamlessly through natural language. While not Supabase directly, it indicates a capability to connect and read/write to a database, which may be useful.
Why this server?
MCP server that allows Claude AI to interact directly with MySQL databases, enabling query execution and table information retrieval through natural language. While not Supabase directly, it indicates a capability to connect and read/write to a database, which may be useful.
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. While not Supabase directly, it indicates a capability to connect and read/write to a database, which may be useful.
Why this server?
Provides read-only access to PostgreSQL databases, enabling LLMs to inspect database schemas and execute read-only SQL queries. Supabase uses PostgreSQL.