Why this server?
This server enables interaction with Supabase PostgreSQL databases through the MCP protocol, allowing seamless integration with Cursor and Windsurf IDEs for secure and validated database management.
Why this server?
An MCP server that connects to Supabase PostgreSQL databases, exposing table schemas as resources and providing tools for data analysis through SQL queries.
Why this server?
This server supports integrations to Supabase's management API, which allows Supabase projects and organizations to be managed by clients.
Why this server?
A Model Context Protocol (MCP) server that provides programmatic access to the Supabase Management API. This server allows AI models and other clients to manage Supabase projects and organizations through a standardized interface.
Why this server?
A Model Context Protocol server that enables Claude to perform Solana token swaps through Jupiter's API, including getting quotes, building transactions, and sending swap transactions on the Solana blockchain (often related to Supabase).
Why this server?
Enables querying Supabase databases and generating TypeScript types through the Model Context Protocol interface, supporting features like schema selection, column filtering, and pagination.
Why this server?
A TypeScript-based MCP server for handling a simple notes system with NextJS that supports creating and summarizing text notes using MCP concepts. It leverages Supabase as its backend.
Why this server?
An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) often connecting to various databases like Supabase through the standardized MCP interface.
Why this server?
An MCP server implementation for DuckDB, often deployed alongside Supabase projects, providing database interaction capabilities through MCP tools.