Skip to main content
Back to the Supabase MCP server

MCP Gateway · OpenCode

Supabase icon

Connect Supabase to OpenCode

OpenCode can query your Supabase database and inspect your projects while you debug in the terminal. Add the Supabase server's hosted URL as a remote server in your OpenCode config and sign in after restarting; from then on, the Speakeasy gateway checks each Supabase call against your role.

Category
Data & analytics
Tools
29
Authentication
OAuth
OpenCode
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 OpenCode 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. OpenCode 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 OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Supabase from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Supabase

Query rows to reproduce a bug

OpenCode runs SQL against the Postgres database to find the rows behind a bug report, so you can reproduce the failure with the same data locally.

execute_sql

Check which extensions are enabled

Before writing code that depends on a Postgres extension, OpenCode lists the extensions in the database so you know whether it is already there.

list_extensions

Target the right project and branch

OpenCode lists your Supabase projects and their development branches, so the next command you run hits the database you meant.

list_projectslist_branches

Tools

29 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

Can Speakeasy block Supabase query results in OpenCode?
Tool output is blocked at the gateway rather than in OpenCode's hooks. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Does Supabase reach OpenCode through a plugin?
No. OpenCode doesn't receive MCP servers from plugins, so you add Supabase to its mcp config block yourself. The observability package is installed separately and the device agent can maintain it.
How do OpenCode users get Supabase?
An admin adds Supabase from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Supabase tools their access allows.
Are Supabase calls from OpenCode 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.