← All connection guides

How to connect Gemini CLI to Supabase

Install Supabase’s official Gemini CLI extension, authorize access and inspect your project through MCP tools.

Free guide · Updated

Based on official documentation · Checked

Ask your agent

Copy the prompt and paste it into your assistant.

Quick answer

Install the Supabase extension for Gemini CLI from the official plugin repository, then complete Supabase authorization when the MCP connection starts. The extension combines Supabase tools with reusable product and Postgres guidance.

1. Choose a development project

Use a Supabase project containing data you can safely inspect and an account authorized for its organization. Keep the project name or reference ready so your first prompt identifies the intended project explicitly.

2. Install the official extension

Run the command published in Supabase’s per-client installation instructions:

gemini extensions install https://github.com/supabase-community/supabase-plugin

3. Start Gemini and authorize Supabase

Open a new interactive session:

gemini

Complete the account connection

Follow the Supabase sign-in flow when the extension’s MCP server requests access. If the connection needs attention, inspect /mcp in Gemini CLI and use its authentication flow for the Supabase server. Review which account and organization you authorize.

Practice

4. Inspect the project before making changes

  1. Ask Gemini CLI to use Supabase MCP to identify your named development project, list its tables and describe the columns of one specific table. Request no data or schema modifications.

Output: The project and table information agree with your Supabase dashboard; the assistant reports actual tool results.

Understand the access scope

Installing the extension does not automatically make every operation read-only. Supabase documents project_ref and read_only=true for a deliberately scoped MCP configuration. Use the official configuration panel if you need that boundary, and remove a redundant bundled connection if switching to manual MCP. Review any configuration before committing it.

Troubleshooting and removal

Extension absent: confirm installation completed and start a fresh Gemini session. Tools present but project missing: check the authorized account and organization. An authentication error does not require exposing a database password or service-role key. Manage or uninstall the extension through Gemini CLI’s extension controls, and revoke the corresponding Supabase authorization when it is no longer needed.

Sources

Read the primary material