Skip to main content
Back to the Supabase MCP server

MCP Gateway · Claude Cowork

Supabase icon

Connect Supabase to Claude Cowork

Cowork suits Supabase work with many steps, such as standing up a project or reviewing every project's health each week. An admin syncs the plugin that carries Supabase into Claude from the organization's marketplace, and Speakeasy checks each Cowork prompt before its step begins.

Category
Data & analytics
Tools
29
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run Supabase MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Supabase call inspected and logged.

Deploy on MCP Gateway

Set up

Add Supabase to Claude Cowork in 4 steps

  1. 01

    Add Supabase from the catalog

    An admin finds Supabase in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Supabase uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Supabase

    Give teams the mcp:connect scope on the Supabase server through team access or a role. Claude Cowork connects to the Supabase server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Supabase from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Supabase needs its own OAuth grant, so each person connects it once. Until they do, Supabase calls fail while the rest of the gateway keeps working.

    From then on, Supabase's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Supabase

Set up a new project end to end

Cowork gets and confirms the cost, creates a project in the organization you choose, and applies the initial migrations once it has started.

get_costcreate_projectapply_migration

Run a weekly project health review

Cowork collects advisory notices and recent logs for each project and writes a weekly summary of security and performance issues to follow up.

list_projectsget_advisorsget_logs

Produce a data dictionary

Cowork lists every table with its columns, primary keys and foreign keys, then writes a data dictionary the whole team can share and keep.

list_tables

Tools

29 tools

Each Supabase tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.

search_docs

Search the Supabase documentation using GraphQL. Must be a valid GraphQL query. You should default to calling this even if you think you already know the answer, since the documentation is always being updated.

list_organizations

Lists all organizations that the user is a member of.

get_organization

Gets details for an organization. Includes subscription plan.

list_projects

Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on.

get_project

Gets details for a Supabase project.

get_cost

Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each. Always repeat the cost to the user and confirm their understanding before proceeding.

See all 29 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every Supabase call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Supabase tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Supabase can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Do Cowork members need GitHub access to get Supabase?
No. Members who receive plugins through Cowork don't need a GitHub invitation. Only the importing admin is added as a marketplace collaborator.
Is Supabase work in Cowork tied to a person?
Yes, once Cowork's OTLP export is set in the Cowork tab's Monitoring settings. The export ties sessions to people and feeds observability.
How do Claude Cowork users get Supabase?
An admin adds Supabase from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Supabase tools their access allows.
Are Supabase calls from Claude Cowork logged?
Yes. Supabase calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Supabase in other clients

AI everywhere.

Control here.