Supabase

Live

OAUTH 2.0

DATABASE OPS

Developer Tools

Projects, database branches, migrations, secrets, and API keys all sit behind the Supabase Management API, reached with per-user OAuth instead of a shared service key.

  • Acts as the user: project and migration changes stay tied to the Supabase account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Supabase
agent · Acme Q3
Run
Which of our Supabase projects are on the free plan and how big are their databases?
S
supabase_list_projects
96ms
Platform agent
3 projects on free: staging-api (412 MB), docs-search (88 MB), demo-eu (1.2 GB, over the 500 MB soft limit).
Sources: 3 projects, 1 organization
supabase
3 projects
18:29
Message Claude...

Tools your DevOps agent reaches for on Supabase, scoped per user.

CALL ANY TOOL
Database ops on the Management API: projects, branches, migrations, SQL queries, edge functions, secrets, and custom domains. Each call carries the user's own OAuth token.
supabase_list_action_runs
List action runs
List all supabase environments action runs for a project, paginated with offset/limit. each run represents an automated clone/pull/health/configure/migrate/seed/deploy pipeline execution (e.g. for a preview branch). returns an array of run objects with id, branch_id, run_steps, workdir, check_run_id, and timestamps.
Parameters
Name
Type
Required
Description
ref
string
Required
The 20-character project reference ID (lowercase letters only). Found in the project's Supabase dashboard URL or Settings > General.
limit
number
Optional
Maximum number of action runs to return per page. KNOWN LIMITATION: Supabase's endpoint requires this as a literal JSON number and does not coerce query-string values, so passing any value here (of any type) currently causes a 400 from Supabase. Omit this field; the API returns all runs without it.
offset
number
Optional
Number of action runs to skip before starting to return results, for pagination. KNOWN LIMITATION: Supabase's endpoint requires this as a literal JSON number and does not coerce query-string values, so passing any value here (of any type) currently causes a 400 from Supabase. Omit this field; the API returns all runs without it.
supabase_get_action_run
Get action run
supabase_read_only_query
Read only query
supabase_bulk_create_secrets
Bulk create secrets
supabase_bulk_update_functions
Bulk update functions
supabase_bulk_delete_secrets
Bulk delete secrets
supabase_remove_project_addon
Remove project addon
supabase_list_available_restore_versions
List available restore versions
supabase_get_action_run_logs
Get action run logs
supabase_run_query
Run query
supabase_create_branch
Create branch
supabase_update_action_run_status
Update action run status
supabase_delete_branch
Delete branch
supabase_remove_project_signing_key
Remove project signing key
supabase_list_backups
List backups
supabase_get_auth_service_config
Get auth service config
supabase_create_login_role
Create login role
supabase_update_auth_service_config
Update auth service config
supabase_delete_function
Delete function
supabase_list_branches
List branches
supabase_get_available_regions
Get available regions
supabase_create_organization
Create organization
supabase_update_backup_schedule
Update backup schedule
supabase_delete_hostname_config
Delete hostname config
supabase_list_buckets
List buckets
supabase_get_backup_schedule
Get backup schedule
supabase_create_project
Create project
supabase_update_branch_config
Update branch config
supabase_delete_invite_external_jit_access
Delete invite external jit access
supabase_list_functions
List functions

For more tools, view docs.

Build your Agent
Drop the toolkit in, point it at the user, and your agent can inspect projects and apply migrations from the first run.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["supabase"], toolNames: ["supabase_list_projects", "supabase_run_query", "supabase_apply_migration"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["supabase"], toolNames: ["supabase_list_projects", "supabase_run_query", "supabase_apply_migration"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["supabase"], toolNames: ["supabase_list_projects", "supabase_run_query", "supabase_apply_migration"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/supabase",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start running Supabase project operations from your workflows.
Project operations
Copy the prompt
Copied
List all projects in org [org_id] with region, plan, and database size.
Copy the prompt
Copied
Create a preview branch off [project_ref] named review-1428.
Copy the prompt
Copied
Pause [project_ref] and confirm when it is fully paused.
Schema and data
Copy the prompt
Copied
Run this query on [project_ref] and summarize the result set.
Copy the prompt
Copied
Apply the pending migration to the review-1428 branch, then diff it against production.
Copy the prompt
Copied
List every table in [project_ref] with row counts.
Access and secrets
Copy the prompt
Copied
Rotate the anon API key for [project_ref] and report the new key id only.
Copy the prompt
Copied
List secrets set on [project_ref] without printing their values.
Copy the prompt
Copied
Show current network restrictions for [project_ref].
SEE HOW AUTH WORKS
Your users connect once. Their Supabase credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Supabase
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Supabase
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Supabase
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Supabase
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Supabase today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Supabase as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Supabase OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Supabase?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Supabase.
What happens when a user revokes Supabase access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent run destructive SQL on a production project?
Only the tools you expose. Migration, delete, and secret tools are separate from the read tools, so a review agent can be limited to list and query while a release agent keeps write access. Scalekit checks the scope before the Management API call, and every statement is attributed to the authorizing user.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""supabase"": {
""url"": ""https://mcp.scalekit.com/supabase"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.supabase]
url = ""https://mcp.scalekit.com/supabase""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""supabase"": {
""url"": ""https://mcp.scalekit.com/supabase"",
""type"": ""http""
}
}
}