Enterprise-managed auth for MCP
The Supabase MCP server now allows Claude to issue identity assertions for enterprise-managed authentication when an identity provider cannot.
137 releases · 2 this month
The Supabase MCP server now allows Claude to issue identity assertions for enterprise-managed authentication when an identity provider cannot.
Explorer provides a unified editor for database management and logs. Users can save investigations as Notebooks to enable reproducible analysis across project teams.
Multigres provides automatic failover for Supabase Postgres and is now available in private alpha for organizations on a paid plan.
OrioleDB, an open-source storage engine for Postgres designed for update-heavy workloads, is now available in public beta on all Supabase plans.
Supabase Compute is now in private alpha, allowing developers to run AI agents and background jobs directly within their Supabase projects.
Supabase now allows users to restrict Personal Access Tokens to specific organizations, projects, and permissions.
Supabase now allows applications to connect to custom Model Context Protocol (MCP) servers. Tool calls are executed as the signed-in user, ensuring existing Row Level Security (RLS) policies are respected.
Supabase has consolidated its .NET libraries into a single repository with a unified versioning scheme.
Supabase released type-safe, composable middleware for Web Fetch handlers, compatible with any fetch runtime or framework.
Supabase released Declarative Schemas 2.0 using pg-delta for its CLI. Generated migrations now automatically incorporate changes to Row Level Security policies, grants, view settings, partitions, and domains.
Supabase now supports an MCP server, allowing AI agents to interact with applications and manage backend tasks directly through Supabase Compute.
OrioleDB is now in Public Beta, allowing users to create OrioleDB projects on Pro, Team, and Enterprise plans. These projects are billed the same as standard Postgres projects and support compute and disk resizing, pause and restore, read replicas, and scheduled backups.
Supabase Middleware 1.0.0 is now available on npm and JSR under semantic versioning. It is a small, MIT-licensed engine for per-request logic on Web Fetch handlers that runs on Supabase Edge Functions, Vercel Functions, Cloudflare Workers, Deno, Bun, and Node 22 or newer.
Supabase Logs is moving to usage-based pricing. Over 90% of projects are within the included limits, and a grace period will extend through early 2027.
The Database Replication section in the dashboard has been renamed to Pipelines. Existing Replication URLs will redirect to the new location, with no changes to API or pipeline behavior.
Supabase Advisors now include service health checks that monitor error rates across Auth, Storage, Edge Functions, and Data APIs. Each check includes a severity level and a direct link to investigate.
Supabase has introduced prepared prompts for four monitoring roles to run in Claude Routines, Codex, Cursor Automations, or other environments, allowing users to hire an agent to watch their projects.
Supabase released an integration with Gemini Enterprise, allowing developers to query Supabase database projects directly using natural language within Gemini Enterprise.
Enterprise IT administrators can now centrally manage access to Supabase in Claude using Okta. Access is scoped to each user's existing permissions.
Read replicas have been moved to Project Settings under the Infrastructure section. The Database Replication section is now dedicated solely to Pipelines destinations.
The supabase-js library now propagates W3C Trace Context to Supabase. This allows client traces and matching Supabase logs to share the same trace_id for easier debugging.
Supabase is now available as a connector on Perplexity Computer. Users can query Postgres data, look up users, and invoke Edge Functions directly from a Perplexity chat.
Supabase has updated Postgres Changes subscriptions to support combining filters with AND, matching on more operators, and selecting specific columns in the payload.
Supabase has released an open-source benchmark to evaluate how well AI coding agents build applications using Supabase.
Supabase has introduced a beta feature allowing users to sign in using their ChatGPT account and connect Supabase within ChatGPT and Codex.
The Supabase Management API logs.all endpoint will be removed on September 23, 2026. Scripts calling this endpoint must migrate to the new ClickHouse-backed logs endpoint, which accepts ClickHouse SQL only.
Specifying an explicit version in CREATE or ALTER EXTENSION is deprecated. Starting August 5, 2026, the version clause is ignored, and the extension's default version is installed with a warning.
Supabase Pipelines is now in public alpha on all paid plans, allowing users to stream Postgres changes to BigQuery in near real time using a managed CDC service configured in the Dashboard.
Self-hosted Supabase will make Envoy the default API gateway, replacing Kong, starting the week of August 9, 2026. Users can opt back into Kong if they rely on its HTTPS listener, custom configuration, or service name.
Supabase has released Unified Logs in open beta, providing a single searchable interface for logs across all Supabase services.
Supabase now blocks all modifications to the realtime schema, causing attempts to create, alter, or drop objects to fail with a permission error. Row Level Security policies on realtime.messages remain functional.
The @supabase/supabase-js library will require TypeScript 5.0 or later starting January 31, 2027, dropping support for TypeScript versions 4.7 through 4.9.
Supabase now supports field-level encryption via CipherStash, allowing for searchable ciphertext without requiring schema changes.
OpenCode now integrates with Supabase, providing automatic MCP setup for agents to access databases, Edge Functions, and logs.
Postgres log_connections will default to off for new projects and existing Free and Pro projects starting July 9, 2026, to reduce log noise. Users can re-enable it via the dashboard or Management API.
Self-hosted Supabase's default API_EXTERNAL_URL will include /auth/v1 starting the week of July 6, 2026. SAML SSO users must update their identity providers to point to the new endpoints.
Supabase Realtime Broadcast now supports sending and receiving binary payloads (bytea) over WebSockets, the REST API, and the database, reducing JSON overhead for sensor streams and image frames.
The June 2026 developer update highlights a $500M Series F funding round, Auth passkeys in beta, the Supabase ChatGPT app, an AI coding agent plugin, and the alpha release of Multigres 0.1.
Multigres v0.1 alpha has been released, providing horizontal scaling and high availability for Postgres.
Starting June 3, 2026, new Free plan projects using Supabase's default SMTP cannot customize auth email templates. Existing projects are unaffected, and customization remains available by configuring a custom SMTP provider.
Supabase Auth now supports passkeys in Beta, enabling passwordless, phishing-resistant sign-in built on WebAuthn using biometrics, device PINs, or hardware security keys.
Supabase project owners and admins can now grant temporary database access via Personal Access Tokens. Access is scoped by role with an expiry of up to 90 days, eliminating the need to disclose passwords.
Self-hosted Supabase's default database image will move from Postgres 15 to Postgres 17 on June 17, 2026. Existing Postgres 15 data does not auto-upgrade, requiring users to run an upgrade script or pin the version.
Supabase support for Postgres 14 ends on July 1, 2026. Remaining Postgres 14 projects will be upgraded automatically, while projects using removed extensions like timescaledb, plv8, or pgjwt will be paused.
Supabase client libraries will drop support for Node.js 20 on June 30, 2026. Users must upgrade to Node.js 22 or later before that date.
The May 2026 developer update introduces custom OAuth/OIDC providers, ISO 27001 certification, the @supabase/server SDK, branching without Git by default, and changes to Data API auto-exposure.
Supabase introduced @supabase/server to provide stateless authentication, RLS-scoped clients, and server-side CORS support. The package is designed to reduce boilerplate code for server-side implementations.
Supabase has made branching without Git the default configuration for all projects, simplifying the development workflow for users.
Starting June 1, 2026, Supabase's OAuth token endpoint will return HTTP 200 instead of 201. Developers should update their integrations to check for any 2XX status rather than a hardcoded 201.
New tables in the public schema will no longer be exposed to the Supabase Data API by default. This change is opt-in immediately, becomes the default for new projects on May 30, 2026, and will be enforced on all projects on October 30, 2026.
The Supabase Dashboard has added an RLS Tester in Feature Preview, allowing users to run SELECT queries as any role, see which RLS policies fire, and debug policies.
Supabase client libraries now automatically retry GET and HEAD requests to PostgREST on transient 520, 503, and network errors. This behavior is enabled by default and can be opted out of per call.
Supabase will begin adding applicable taxes, such as VAT, GST, and sales tax, to invoices based on the organization's billing address, rolling out from May 1 to June 30, 2026.
Supabase is transferring the maintenance and ownership of the Stripe Sync Engine to Stripe.
Supabase released an open-source set of instructions designed to teach AI coding agents how to build on Supabase correctly.
Supabase Auth now supports custom OpenID Connect (OIDC) providers, enabling users to connect identity providers like GitHub Enterprise and regional services to their projects.
Supabase has joined the Stripe Projects developer preview as a co-design partner.
Supabase Edge Functions now rate-limit recursive and nested function-to-function calls at a minimum of 5,000 requests per minute per chain. Inbound and external requests are unaffected.
Supabase Pro users can now stream their database logs to external logging backends for centralized debugging.
The Supabase Data API will stop returning the OpenAPI spec to anon-key requests, starting February 11, 2026, for new projects and April 8, 2026, for all projects.
Postgres, auth, storage, realtime and edge functions.
Other Supabase products: Supabase CLI
| Release-notes page | Site | Feed |
|---|---|---|
| supabase-js releases github.com | github.com | RSS |
| Auth releases github.com | github.com | RSS |
| Changelog supabase.com | supabase.com | None |
| CLI releases github.com | github.com | RSS |
| Postgres image releases github.com | github.com | RSS |