Supabase is an open source Firebase alternative, providing a PostgreSQL database, authentication, instant APIs, realtime subscriptions, and storage.
Why this server?
Enables safely interacting with Supabase databases, executing SQL queries, managing database schemas, accessing the Supabase Management API, and using the Supabase Auth Admin SDK for user management. Includes safety controls for different risk levels of operations.
Why this server?
Acts as a bridge between MCP clients and Supabase services, providing database operations, storage management, edge function invocation, project/organization management, and user authentication/management
Why this server?
Integrates with Supabase for database operations including vector search for code examples and game resources
Why this server?
Enables interaction with self-hosted Supabase instances, providing tools for database introspection, SQL query execution, schema management, migrations, auth user management, storage bucket operations, and TypeScript type generation.
Why this server?
Automatically uploads clipboard images to Supabase Storage and returns public URLs, with features for managing stored files including automatic cleanup of old files.
Why this server?
Provides tools for database operations in Supabase including querying data, inserting records, updating records, and deleting records, allowing interaction with Supabase tables from a NextJS application.
Why this server?
Enables querying Supabase database tables with filtering options and generating TypeScript types from database schemas
Why this server?
Provides programmatic access to the Supabase Management API, allowing AI models and other clients to manage Supabase projects and organizations. Capabilities include listing, creating and deleting projects, retrieving project API keys, and managing organizations.
Why this server?
Provides database integration with Supabase services
Why this server?
Enables LLMs to perform database queries and operations on Supabase projects via PostgREST API
Why this server?
Supported for Auth integration in React projects with context-aware implementation memory
Why this server?
Used for storing and serving images related to the project documentation
Why this server?
Implements authentication through Supabase to securely manage user access to the personal knowledge base.
Why this server?
Provides vector database capabilities for storing and retrieving crawled web content with pgvector extension
Why this server?
Enables interaction with Supabase databases, providing tools for reading, creating, updating, and deleting records in tables with filtering capabilities and type-safe request/response handling.
Why this server?
Connects to a Supabase PostgreSQL database, exposing table schemas as resources and providing tools for data analysis, SQL querying, and relationship exploration
Why this server?
Provides a managed PostgreSQL database solution with vector storage capabilities for memory persistence
Why this server?
Integrates with Supabase PostgreSQL database, supporting schema inspection, SQL execution, and session pooler connections
Why this server?
Enables CRUD operations on Postgres tables, including querying data with filters, inserting data, updating data, deleting data, and listing tables in a Supabase project.
Why this server?
Enables safe interaction with Supabase databases through SQL query execution, database management tools, Supabase Management API access, and Auth Admin operations like user management. Supports both read-only and data modification operations with built-in safety controls.
Why this server?
Provides enhanced database interactions through Supabase, including SQL query processing, PostgREST API access, SQL to REST conversion, and optimized response formatting for UI components, with improved error handling and authentication.
Why this server?
Provides persistent storage for contact events and rate limiting data, allowing the MCP server to store and retrieve logged authority contact information.
Why this server?
Uses Supabase PostgreSQL database for storage and retrieval of WebDNA documentation, with support for migrations and full-text search
Why this server?
Connects to a Supabase Postgres database to execute SQL queries generated from user questions and retrieve relevant data.
Why this server?
Compatible with Supabase + MCP integration, allowing models to query Supabase-managed PostgreSQL databases
Why this server?
Synchronizes vector embeddings between Supabase tables, monitoring changes in the 'proyectos' table and updating the 'proyecto_vector' table with vector embeddings for efficient multi-tenant search capabilities.
Why this server?
Connects AI assistants like GitHub Copilot to Supabase databases, allowing them to understand database schemas, know about tables and relationships, assist with query writing, and provide context-aware suggestions related to the data model.
Why this server?
Allows querying of the feature_suggestions table in a Supabase database, with optional limits on the number of records returned.
Why this server?
Built-in support for Supabase vector database, enabling storage and retrieval of vector embeddings for AI applications.
Why this server?
Provides full administrative control over a Supabase PostgreSQL database, including tools for table operations, record management, schema modifications, indexes, constraints, database functions, triggers, security policies, and storage management.
Why this server?
Stores knowledge graph data in Supabase with support for entities, relations, and database-level locking for concurrent access