---
title: "Enterprise-managed auth for the Supabase MCP server"
url: https://daily.dev/posts/enterprise-managed-auth-for-the-supabase-mcp-server-rigimbuhf
source_url: https://supabase.com/blog/enterprise-managed-auth-for-the-supabase-mcp-server
type: article
source: "Supabase"
published: 2026-08-24T19:44:52.505Z
updated: 2026-08-25T12:16:05.043Z
tags: ["authentication", "mcp", "claude", "supabase", "okta"]
reading_time: 2
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise-managed auth for the Supabase MCP server

**[Supabase](https://daily.dev/sources/supabase)** · 2 min read · 0 upvotes · 0 comments

## Summary

Supabase now offers enterprise-managed authentication for its MCP server, built with Anthropic and Okta, generally available on Team and Enterprise plans. IT admins can grant, restrict, and revoke access to Supabase within Claude directly from Okta, scoped to each employee's existing Supabase role and permissions. Previously, each user had to individually approve OAuth consent and only organization owners could authorize the connection; now a single admin authorization covers the whole organization, with onboarding, offboarding, and access reviews flowing through the identity provider. SCIM-based provisioning for the platform is planned next.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://supabase.com/blog/enterprise-managed-auth-for-the-supabase-mcp-server>

## Questions this post answers

### How does enterprise-managed auth work for the Supabase MCP server with Claude?

An IT admin authorizes the Supabase connector once through Okta, and every employee signing into Claude gets Supabase access automatically scoped to their existing Supabase role and permissions. This replaces the previous flow where each person had to approve their own OAuth consent and only organization owners could authorize the connection at all. It requires a Supabase Team or Enterprise plan with Okta SSO enabled and a Claude Team or Enterprise plan.

_Teams rolling out AI coding tools across an org can track integration changes like this on daily.dev._

### What happens to someone's Supabase access in Claude when they're offboarded in Okta?

Offboarding someone in Okta automatically removes their Supabase access in Claude, since access is tied to identity provider group membership rather than individual manual grants. This lets security teams run onboarding, offboarding, and access reviews for Supabase inside Claude through the same identity provider workflows they already use for other applications.

_Security teams standardizing AI tool access reviews follow updates like this via daily.dev._

## Similar posts on daily.dev

- [MCP gets its missing enterprise authorization layer](https://daily.dev/posts/mcp-gets-its-missing-enterprise-authorization-layer-9gkkeg9th) · The New Stack · 1 upvotes · 0 comments

---

Tags: [#authentication](https://daily.dev/tags/authentication), [#mcp](https://daily.dev/tags/mcp), [#claude](https://daily.dev/tags/claude), [#supabase](https://daily.dev/tags/supabase), [#okta](https://daily.dev/tags/okta)

[View this post on daily.dev](https://daily.dev/posts/enterprise-managed-auth-for-the-supabase-mcp-server-rigimbuhf)