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 provides tools for interacting with Supabase databases, storage, and edge functions.
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 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?
This TypeScript-based MCP server implements a simple notes system, allowing the creation, listing, and summarization of text notes using Model Context Protocol (MCP).
Why this server?
A TypeScript-based MCP server that connects to FHIR servers, allowing access to healthcare data via fhir:// URIs and providing search capabilities for FHIR resources.