Supabase Enterprise-managed auth for the Supabase MCP server Is Generally Available.

Supabase is giving enterprise IT teams centralized control over how employees access its platform from Claude. The new Enterprise-managed auth for the Supabase MCP server lets administrators authorize the connector through Okta once, enforce access across an organization, and keep every user limited to their existing Supabase permissions.

The feature is generally available on Supabase Team and Enterprise plans, according to the company’s official announcement. It was built with Anthropic and Okta, and is intended to make AI-assisted database work fit established identity, onboarding, and security review processes.

Previously, every employee connecting Claude to Supabase had to approve an individual OAuth consent flow. More significantly, only Supabase organization owners could authorize the connection. That created friction for developers and read-only users, while leaving IT departments to oversee a collection of individual grants.

With the new system, an administrator approves the Supabase connector centrally. Employees who subsequently sign into Claude find the connector ready to use, without having to establish their own separate authorization.

Central authorization does not give every employee the same level of access. Supabase says requests are tied to the person using Claude, with queries and management actions evaluated against that person’s existing Supabase role.

In practice, that means:

• Developers can use the MCP connection with their current developer permissions.
• Read-only members remain read-only when working through Claude.
• Queries and management actions cannot exceed what the employee could do by signing into Supabase directly.
• Access can be restricted to a designated Okta group rather than granted employee by employee.

This distinction matters for teams connecting AI assistants to production data. A centrally enabled connector could otherwise become an authorization shortcut, allowing an assistant to reach projects or perform actions that its user could not access through the normal dashboard. Supabase’s approach instead makes Claude another interface governed by existing identity and project controls.

The release extends Supabase’s broader push to connect its Postgres platform with AI tools. It follows the Supabase Perplexity Computer connector, which brought project data into another agentic environment. This update focuses less on adding a new destination and more on making an existing AI connection manageable inside larger organizations.

Okta becomes the control point for deciding who may use Supabase through Claude. Security teams can assign access through group membership, review one centrally enforced policy, and remove access through the same identity workflows they already use for other company applications.

Offboarding is a clear example. When an employee is removed in Okta, their Supabase access through Claude is removed with it. Administrators no longer need to identify and revoke a separate, user-authorized connector after the person leaves the organization.

The model also gives compliance teams a cleaner answer during access reviews. Rather than auditing a set of individual OAuth approvals, they can inspect the organization’s identity policy and confirm that activity remains bound to each person’s Supabase role. The company positions this alongside its existing SSO, project-scoped roles, and SOC 2 and HIPAA compliance support.

For small businesses, the immediate value depends on how formal their identity infrastructure has become. Teams already using Okta and Claude for development or database operations gain less manual administration and a more predictable offboarding path. Smaller organizations without Okta SSO will not be able to use this release in its current form.

Supabase says SCIM-based provisioning for its platform is on the roadmap. No availability date was provided, so the current release should be understood as centralized connector authorization and access enforcement, not a complete replacement for every user provisioning workflow.

What is Enterprise-managed auth for the Supabase MCP server?

It is a centralized authentication system that lets IT administrators control employee access to Supabase from Claude through Okta. The Supabase MCP server carries out each request using the individual employee’s existing Supabase role and permissions.

Which Supabase plans support enterprise-managed authentication?

The feature is generally available for organizations on Supabase Team and Enterprise plans with Okta SSO enabled. Supabase did not announce separate add-on pricing in its post.

How does this change the previous authorization process?

Previously, users approved their own OAuth consent, and only Supabase organization owners could authorize the connection. Now an administrator can authorize the connector once for the organization, while each employee’s activity remains restricted to that employee’s existing permissions.