Supabase

Manage databases, authentication, and storage metadata in Supabase.

Family	Category	Sub-type	Auth type	Trending score
Developer Platform	developer	backend	bearer_token	81

Overview

Product URL	API docs	Supported features
https://supabase.com/	https://supabase.com/docs/guides/api	tool_discovery, health_check

Setup

1. Install the connector instance.
2. Store the provider token or connection secret.
3. Sync the tools and test the connection.
4. Review approval-gated write tools before running them.

Auth & Configuration

Field	Required	Type	Notes
projectRef	No	string	Optional Supabase project ref used to scope project-specific tools.

Example config

{
  "projectRef": "abcdefghijklmnop"
}

• Set projectRef only when you want to scope project-specific tools.

Available Tools

Tool	Requires approval	Description
list_projects	No	List Supabase projects.
get_project	No	Retrieve a Supabase project by ref.
list_auth_providers	No	List SSO providers configured for a Supabase project.
list_third_party_auth	No	List third-party auth integrations for a Supabase project.

Use list_projects for the main execution example below because it is safe to run without approval.

Examples

Install

CLI

chainabit connectors install supabase --name "Supabase" --config '{"projectRef":"abcdefghijklmnop"}'

cURL

curl -X POST "$BASE_URL/connectors/instances" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "connectorKey": "supabase",
  "displayName": "Supabase",
  "config": {
    "projectRef": "abcdefghijklmnop"
  }
}'

JavaScript

const response = await fetch(`${BASE_URL}/connectors/instances`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "connectorKey": "supabase",
  "displayName": "Supabase",
  "config": {
    "projectRef": "abcdefghijklmnop"
  }
}),
});

Credentials

CLI

chainabit connectors auth <instance-id>

cURL

curl -X POST "$BASE_URL/connectors/instances/<instance-id>/credentials" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "credType": "bearer_token",
  "credentials": {
    "token": "YOUR_BEARER_TOKEN"
  }
}'

JavaScript

await fetch(`${BASE_URL}/connectors/instances/<instance-id>/credentials`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "credType": "bearer_token",
  "credentials": {
    "token": "YOUR_BEARER_TOKEN"
  }
}),
});

Execute

CLI

chainabit connectors exec <instance-id> list_projects --input '{}'

cURL

curl -X POST "$BASE_URL/connectors/instances/<instance-id>/tools/tool_list_projects/execute" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {}
}'

JavaScript

const response = await fetch(
  `${BASE_URL}/connectors/instances/<instance-id>/tools/tool_list_projects/execute`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${TOKEN}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
  "input": {}
}),
  },
);

Security Notes

• Keep tokens, API keys, and connection strings in the encrypted credentials vault.
• Do not allow arbitrary server URLs for remote MCP connectors.
• Set projectRef only when you want to scope project-specific tools.

Troubleshooting

• If the health check fails, verify the token scope or credential payload and try again.
• If the tool list is empty, re-run sync-tools after storing the latest credentials.

Back to the catalog