Search for:
Why this server?
Offers persistent memory with vector search capabilities, which could be beneficial for managing and querying data, similar to how Supabase provides database functionality.
Why this server?
Connects to Supabase PostgreSQL databases, exposing table schemas and providing tools for data analysis through SQL queries.
Why this server?
Provides tools for managing JIRA issues through a simple interface, and could work in conjunction with Supabase for project or task management.
Why this server?
Provides programmatic access to the Supabase Management API, enabling AI models to manage Supabase projects and organizations.
Why this server?
Provides database interaction and business intelligence capabilities through SQLite, offering a simple and portable database solution.
Why this server?
Provides memory/knowledge graph storage capabilities using Supabase, enabling multiple Claude instances to safely share and maintain a knowledge graph.
Why this server?
Uses Supabase to provide memory and knowledge graph storage, with database-level locking for safe concurrent access.
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?
A TypeScript-based MCP server for handling a simple notes system with NextJS that supports creating and summarizing text notes using MCP concepts.