| Ecosystem | 1 | 0 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 12 decomposed | 9 decomposed |
| Times Matched | 0 | 0 |
Aggregates calendar events from heterogeneous sources (Google Calendar, Outlook, Office 365, iCloud, CalDAV, ICS) into a single normalized event schema through provider-specific adapters. Each provider implements a standardized interface that translates proprietary event formats (Google's calendar API response structure, Microsoft Graph event objects, iCalendar RFC 5545 format) into a unified internal representation, enabling downstream tools to operate on events without provider-specific branching logic.
Unique: Implements provider-agnostic adapter pattern with RFC 5545 iCalendar as the internal canonical format, allowing CalDAV and ICS sources to be treated as first-class citizens alongside OAuth2 APIs without special-casing; most competitors (Zapier, IFTTT) treat CalDAV as a secondary integration
vs alternatives: Supports self-hosted CalDAV and ICS sources natively without cloud dependency, whereas Zapier and Make.com require paid connectors and don't support local ICS files
Exposes aggregated calendar operations as MCP (Model Context Protocol) tools that Claude and other LLM clients can invoke directly. Implements the MCP tool schema specification with JSON-RPC 2.0 transport, allowing LLMs to call calendar functions (list events, create event, update event, delete event) with structured arguments and receive typed responses. The MCP server runs as a standalone process that Claude Desktop or Cline can discover and communicate with via stdio or HTTP transport.
Unique: Implements full MCP tool specification with stdio and HTTP transport options, allowing keeper.sh to be discovered and used by Claude Desktop without custom client code; includes schema validation and error handling for malformed tool calls
vs alternatives: Native MCP support means zero integration code required in Claude Desktop (just add to config.json), whereas Zapier and Make.com require custom webhook setup and don't support real-time LLM agent interaction
Exposes webhook endpoints that receive real-time event change notifications from calendar providers (Google Calendar push notifications, Microsoft Graph change notifications) and processes them to update the aggregated calendar state. Implements webhook signature verification to ensure authenticity, handles webhook retries and exponential backoff for failed deliveries, and maintains a webhook delivery log. Supports filtering notifications by event type (created, updated, deleted) and calendar source.
Unique: Implements provider-agnostic webhook handling with signature verification and delivery logging, supporting both Google Calendar and Microsoft Graph push notifications; includes webhook filtering by event type
vs alternatives: Provides real-time event notifications via webhooks, whereas polling-based sync has 1-hour latency by default
Exports aggregated calendar events to multiple formats (ICS/iCalendar, JSON, CSV) with configurable filtering and field selection. Implements RFC 5545 compliant ICS generation with proper VEVENT component structure, timezone definitions, and recurrence rules. Supports exporting to file or HTTP response stream. Handles large exports (>100MB) with streaming to avoid memory exhaustion.
Unique: Implements RFC 5545 compliant ICS export with streaming support for large calendars, supporting multiple output formats (ICS, JSON, CSV) with configurable field selection
vs alternatives: Provides streaming export for large calendars without memory exhaustion, whereas most calendar apps load entire calendar into memory before export
Manages OAuth2 authorization flows for Google Calendar and Microsoft Graph (Outlook/Office 365) with automatic token refresh and secure credential persistence. Implements the OAuth2 authorization code flow with PKCE (Proof Key for Code Exchange) for public clients, stores refresh tokens in encrypted local storage or environment variables, and automatically refreshes access tokens before expiration to maintain uninterrupted calendar access. Handles token revocation and re-authorization on credential invalidation.
Unique: Implements PKCE-protected OAuth2 flow with automatic token refresh and provider-agnostic credential abstraction, allowing multiple OAuth2 providers to be managed through a single interface; includes explicit token revocation support
vs alternatives: Handles token refresh automatically without user intervention, whereas manual OAuth2 implementations require developers to track expiration times and implement refresh logic separately
Implements the CalDAV protocol (RFC 4791) for reading and writing calendar events to CalDAV servers (e.g., Nextcloud, Radicale, Fruux). Supports automatic server discovery via DNS SRV records and well-known URIs (.well-known/caldav), handles WebDAV PROPFIND and REPORT operations to enumerate calendars and fetch events, and implements iCalendar serialization/deserialization for event data. Supports both Basic and Digest HTTP authentication for CalDAV server access.
Unique: Implements full CalDAV protocol stack with automatic server discovery via DNS SRV and .well-known URIs, treating CalDAV as a first-class provider alongside OAuth2 APIs; includes WebDAV PROPFIND support for calendar enumeration
vs alternatives: Supports self-hosted CalDAV servers natively without requiring cloud connectors, whereas most calendar aggregators (Fantastical, Outlook) require manual CalDAV URL entry and don't support automatic discovery
Parses iCalendar (ICS) files from local paths or HTTP URLs using RFC 5545 compliant parsing, extracting VEVENT components and normalizing them into the unified event schema. Supports recurring events (RRULE), timezone definitions (VTIMEZONE), and attendee lists (ATTENDEE). Implements periodic polling to detect changes in remote ICS files and sync new/updated events into the aggregated calendar. Handles ICS file encoding variations (UTF-8, ISO-8859-1) and malformed iCalendar data gracefully.
Unique: Implements RFC 5545 compliant ICS parsing with RRULE expansion and VTIMEZONE support, treating ICS files as a first-class calendar source with automatic polling and change detection; most calendar tools treat ICS as a one-time import format
vs alternatives: Supports continuous ICS file synchronization with polling, whereas most calendar applications only support one-time ICS import without change detection
Provides create, read, update, and delete operations for calendar events across all aggregated providers through a unified API. Implements conflict detection by checking for overlapping events before creation/update, validates event properties (required fields, time ranges), and routes operations to the appropriate provider backend. Handles provider-specific constraints (e.g., Google Calendar's 5000 event limit per calendar, Microsoft's attendee limits) and returns detailed error messages for failed operations.
Unique: Implements unified CRUD interface with automatic provider routing and conflict detection, abstracting away provider-specific API differences; includes explicit conflict detection before event creation
vs alternatives: Provides conflict detection as a built-in operation, whereas most calendar APIs require separate queries to check for overlaps
+4 more capabilities
Executes SQL queries against Supabase PostgreSQL instances through the Model Context Protocol, translating natural language or structured query requests into parameterized SQL statements. Uses MCP's tool-calling interface to expose database operations as callable functions with schema validation, enabling LLM agents to perform CRUD operations, joins, and aggregations with automatic connection pooling and credential management through Supabase client SDK.
Unique: Exposes Supabase PostgreSQL as MCP tools with automatic credential injection from Supabase client SDK, eliminating manual connection string management and enabling seamless LLM-to-database queries within Claude or compatible agents
vs alternatives: Tighter integration than generic SQL MCP servers because it leverages Supabase's built-in authentication and connection pooling rather than requiring separate database credential configuration
Exposes Supabase Auth session state and user metadata through MCP tools, allowing agents to inspect current authentication context, retrieve user profiles, and trigger auth-related operations. Integrates with Supabase's JWT-based auth system to validate sessions and access user claims without re-authenticating, using the Supabase client's built-in session management.
Unique: Integrates Supabase's JWT-based auth system directly into MCP tool interface, allowing agents to inspect and act on auth state without managing separate credential stores or re-authentication flows
vs alternatives: More seamless than generic auth MCP servers because it leverages Supabase's built-in session management and avoids redundant credential passing between agent and auth system
Invokes Supabase Edge Functions (serverless TypeScript/JavaScript functions) through MCP tools, passing parameters and receiving results with optional streaming support. Uses Supabase's edge function HTTP API to trigger functions with automatic authentication headers and response parsing, enabling agents to execute custom business logic without embedding it in the agent itself.
Supabase scores higher at 42/100 vs keeper.sh at 37/100.
Need something different?
Search the match graph →© 2026 Unfragile. Stronger through disorder.
Unique: Exposes Supabase Edge Functions as MCP tools with automatic authentication and response parsing, allowing agents to invoke custom serverless logic without managing HTTP clients or credential injection
vs alternatives: More integrated than generic HTTP MCP tools because it handles Supabase-specific authentication, error handling, and response formatting automatically
Subscribes to real-time changes on Supabase tables through MCP's event streaming interface, using Supabase's PostgreSQL LISTEN/NOTIFY mechanism to push INSERT, UPDATE, and DELETE events to agents. Maintains persistent WebSocket connections and filters events by table and row-level policies, enabling agents to react to database changes without polling.
Unique: Bridges Supabase's PostgreSQL LISTEN/NOTIFY real-time system with MCP's tool interface, enabling agents to subscribe to database changes without managing WebSocket connections or event serialization
vs alternatives: More efficient than polling-based approaches because it uses Supabase's native real-time infrastructure rather than repeated database queries
Manages files in Supabase Storage buckets through MCP tools, supporting upload, download, list, and delete operations with automatic authentication and path-based access control. Uses Supabase's S3-compatible storage API with built-in support for public/private buckets and signed URLs for temporary access, enabling agents to handle file I/O without managing cloud storage credentials.
Unique: Exposes Supabase Storage's S3-compatible API as MCP tools with automatic authentication and signed URL generation, eliminating the need for agents to manage cloud storage credentials or generate temporary access tokens
vs alternatives: More integrated than generic S3 MCP tools because it leverages Supabase's built-in bucket policies and authentication rather than requiring separate AWS credentials
Performs semantic similarity searches on vector embeddings stored in Supabase PostgreSQL using pgvector extension, translating natural language queries into embedding vectors and executing cosine/L2 distance searches. Integrates with embedding providers (OpenAI, Cohere) or uses pre-computed embeddings, enabling agents to retrieve semantically similar documents or records without full-text search limitations.
Unique: Integrates pgvector directly into MCP tools with automatic embedding generation and distance calculation, enabling agents to perform semantic search without managing separate vector database infrastructure
vs alternatives: More efficient than external vector databases (Pinecone, Weaviate) for Supabase users because it colocates embeddings with relational data, reducing network latency and simplifying data synchronization
Exposes Supabase database schema information through MCP tools, allowing agents to discover table structures, column types, constraints, and relationships without manual schema documentation. Queries PostgreSQL information_schema and Supabase metadata tables to dynamically generate schema descriptions, enabling agents to construct valid queries and understand data relationships.
Unique: Queries Supabase's PostgreSQL information_schema directly through MCP tools, enabling agents to dynamically discover and adapt to database schemas without pre-configured schema definitions
vs alternatives: More flexible than static schema definitions because it reflects live database state, including recent migrations or schema changes
Enforces Supabase Row-Level Security policies within agent queries, ensuring that agents can only access rows permitted by RLS rules defined in the database. Evaluates policies based on authenticated user context (JWT claims, user ID) and applies WHERE clause filters automatically, preventing unauthorized data access at the database layer rather than application layer.
Unique: Delegates authorization enforcement to PostgreSQL RLS policies rather than implementing authorization in agent code, ensuring that data access rules are centralized and cannot be bypassed by agent logic
vs alternatives: More secure than application-level authorization because RLS is enforced at the database layer, preventing accidental data leaks even if agent code has bugs
+1 more capabilities