Provider REST API

20 actions

Connect Claude to Supabase

Work with projects, databases, auth, storage, and logs. Toolspoke puts 20 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: Access token
Actions exposed: 20
Cost per call (typical): 1 credit
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Supabase
Open the marketplace in your workspace, add Supabase to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with access token. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Supabase shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Supabase asks for

Access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Personal access tokenRequired: Supabase dashboard → Account → Access Tokens. The token inherits your own org and project permissions.; sbp_…

What Claude can do in Supabase

20 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 18Reads
Writes: 2Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

list_projects
List the Supabase projects this access token can reach, with their project ref, region and status. Call this first - every other action needs a project ref.
get_project
Fetch one project's name, region, status and Postgres version. Use when you need to confirm a project is active before querying it.
check_health
Report the health of a project's services (auth, db, pooler, realtime, rest, storage). Use this when queries or API calls to a project are failing and you need to tell an outage from a bad query.
list_tables
List the tables and views in a project's database with their row estimates and whether row-level security is on. Use this to discover the schema before writing SQL, instead of guessing table names.
list_table_columns
List tables and views together with every column's name, type and nullability. Use list_tables when you only need the table names - this response is several times larger.
list_migrations
List the migration history recorded for a project, newest last. Use this to see what schema changes have already been applied.
list_advisors
Run Supabase's security or performance advisors and return the outstanding lints - missing RLS policies, exposed views, unindexed foreign keys, unused indexes. Call the security advisor after any migration that adds tables or policies.
list_edge_functions
List a project's deployed edge functions with their slug, status and version. Use this before reading or debugging function logs.
list_storage_buckets
List a project's storage buckets and whether each one is public. Use this to check bucket names and public exposure before writing storage code.
generate_typescript_types
Generate TypeScript types for a project's database schema, ready to paste into a Database type file. Use this after a schema change so client code stays in sync.
logs_api
API and edge request logs: method, path and response status for each request. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_postgres
Postgres server logs, including query errors and their severity. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_edge_function
Edge function request logs, with per-invocation execution time and status. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_edge_function_runtime
Output written by edge function code itself - console logs and uncaught errors. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_auth
Auth service logs: sign-ins, token refreshes, and the reason a login failed. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_storage
Storage service logs. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_realtime
Realtime service logs. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.
logs_branch_action
Branch workflow run logs. Only the last minute is returned unless you pass a time range. Returns the 50 most recent lines.

Writes

Creates or updates something on the other side.

query
Run SQL against the project's Postgres database and return the result rows. Read-only by default; set read_only to false only when the user asked for a write. Always add an explicit LIMIT - the full result set is returned to you verbatim.
apply_migration
Apply a named DDL migration to the project's database and record it in the migration history. Use this for schema changes (CREATE TABLE, ALTER TABLE, policies) rather than the query action, so the change is versioned. This writes to production - confirm with the user first.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 20 actions above are the whole of it. A call to any other name is refused before it reaches Supabase rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
Nothing here deletes: This connector writes to Supabase, but nothing in it deletes or permanently alters anything.
It reaches no further than your credential: Toolspoke holds no access to Supabase of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Supabase: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Supabase. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Supabase's own rate limits. A call that Supabase refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Supabase?

20 named actions: 18 that only read and 2 that write. They include list_projects, get_project and check_health. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Supabase connector need?

Access token. The connector asks for personal access token. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Supabase connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 20 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Supabase connector not do?

The 20 actions above are the whole of it. A call to any other name is refused before it reaches Supabase rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. This connector writes to Supabase, but nothing in it deletes or permanently alters anything. Toolspoke holds no access to Supabase of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Supabase. An agent has to ask. Toolspoke does not retry, queue or back off around Supabase's own rate limits. A call that Supabase refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Supabase's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Supabase?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More database connectors

Browse all of them