Supabase

Developer tools

Supabase for AI agents. Managed auth, ready-made tools.

List projects, run SQL, read logs and edge functions, and generate types in your users' Supabase projects.

About Supabase

With the Supabase connector, your agent works with each user’s own Supabase projects through Agent200: it lists projects, runs SQL against the database, reads logs and edge functions, and generates TypeScript types from the schema. Every user connects their own account through managed OAuth.

Supabase is a Postgres development platform that adds authentication, storage, edge functions and realtime to every project’s database.

Tools

What your agent can do in Supabase.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Supabase connection.

  • List projects

    Read
    supabase_list_projects

    List the projects the connected user can access.

  • Run a read-only query

    Read
    supabase_run_read_only_query

    Run a SQL query that can read but never change the database.

  • Run a SQL query

    Write
    supabase_run_query

    Run a SQL statement, including ones that change data or schema.

  • List edge functions

    Read
    supabase_list_functions

    List a project's edge functions and their status.

  • Get logs

    Read
    supabase_get_logs

    Read a project's logs for a time range.

  • Generate TypeScript types

    Read
    supabase_get_typescript_types

    Generate TypeScript types from the database schema.

Control

Limits you can set.

You decide what your agent may do in Supabase, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Keep supabase_run_read_only_query and switch off supabase_run_query so your agent can read the database but never change it.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use. A call outside them is refused.

Get started

Connect Supabase
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Supabase

    Each end user authorizes their own Supabase account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Supabase account, once.
    const connection = await agent200
      .user("user_123")
      .connect("supabase");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Supabase tools

    Name the user, the model and the tools. The model decides which Supabase tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "How many users signed up yesterday",
        tools: ["supabase"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Supabase's own page. You never see or store their Supabase credentials.

  • What access is requested

    The user picks the organization to connect, and Supabase shows the scopes requested, such as reading projects or reading and writing the database.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Supabase connector and how to use it.

Agent brief
Connector: Supabase, through Agent200. In code: "supabase".
What it does: List projects, run SQL, read logs and edge functions, and generate types in your users' Supabase projects.
Page: https://www.agent200.com/tools/supabase/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Supabase's own page, through the authorization link Agent200 returns. Never ask a user for a Supabase password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: supabase_list_projects, supabase_run_read_only_query, supabase_list_functions, supabase_get_logs, supabase_get_typescript_types. Write tools: supabase_run_query. Name "supabase" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/supabase/framework/claude/
   https://www.agent200.com/tools/supabase/framework/chatgpt/
   https://www.agent200.com/tools/supabase/framework/claude-code/
   https://www.agent200.com/tools/supabase/framework/muse/
   https://www.agent200.com/tools/supabase/framework/grok-bot/
   https://www.agent200.com/tools/supabase/framework/openai-dots/
   https://www.agent200.com/tools/supabase/framework/claude-duet/
   https://www.agent200.com/tools/supabase/framework/hermes-agent/
   https://www.agent200.com/tools/supabase/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/supabase.md

Guides

Use Supabase with the AI you build on.

Step-by-step setup for Supabase with a specific model, assistant or agent framework.

FAQ

Supabase and Agent200, answered.

Who handles the Supabase OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Supabase.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Supabase connection, never another user's. It cannot reach anything the user or Supabase has not authorized.

Can I limit what my agent can do in Supabase?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Supabase.
Your agent does the rest.

Your users connect their own Supabase accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)