Skip to main content
Back to the Supabase MCP server

MCP Gateway · Cursor

Supabase icon

Connect Supabase to Cursor

Cursor can read and deploy Supabase Edge Functions and check your project for problems from the editor. The Speakeasy MCP Gateway gives each developer the same Supabase URL, checks every tool call against their role, and records the developer's email with each one.

Category
Data & analytics
Tools
29
Authentication
OAuth
Cursor
Editor and terminal

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 Cursor 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. The organization gateway works out each person's servers from their live access, so granting access adds Supabase to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Supabase from Cursor

    The first time Cursor 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 Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Supabase

Edit and redeploy an Edge Function

Cursor pulls the current files of an Edge Function into the editor and, once you've made the change, deploys it as a new version.

get_edge_functiondeploy_edge_function

Work through project advisories

Cursor fetches the project's security and performance advisory notices, with their remediation links, and helps you fix each one in your code or SQL.

get_advisors

Fill in the frontend environment file

Get the project's API URL and publishable keys so Cursor can complete the environment file for the frontend you're building.

get_project_urlget_publishable_keys

Tools

29 tools

Each Supabase tool can be allowed or denied per team and role at the MCP Gateway before Cursor 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 Cursor

The gateway covers every client the same way. The rest depends on what Cursor 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 Cursor. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Do Speakeasy's hooks run when a Cursor Cloud agent uses Supabase?
Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
Can Speakeasy stop Cursor from deploying an Edge Function?
Yes. Cursor hooks send each tool call to Speakeasy, which allows or denies it before Cursor runs it, and they fail closed. An admin can also deny deploy_edge_function for a role at the gateway.
How do Cursor users get Supabase?
An admin adds Supabase from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Supabase tools their access allows.
Are Supabase calls from Cursor 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.