Back to the marketplace · Connector
Supabase Remote (OAuth)
Supabase's official hosted remote MCP service, connected in read-only mode (read_only=true) by default: browse projects and tables, run queries as a read-only database user, read logs and advisors, and view Edge Functions. Authorized by the host via OAuth (dynamic client registration + PKCE) with automatic token refresh; no access token needs to be entered.
Copy this sentence and send it to any colleague in Teloa:In Teloa, open Marketplace, search for "Supabase Remote (OAuth)" and add it (entry teloa.mcp-supabase-remote).
- Source
- Teloa official · Original source
- License
- LicenseRef-Supabase-Terms
License files: LICENSE - Review
- Reviewed by Teloa on 2026-09-26
- Compatibility
- Needs configuration · Teloa >=0.2.0-alpha.6 · DSH 0.1.7-rc.1
- The owner must complete OAuth authorization in a browser from Market → Connections; server deployments must set oauth.publicCallbackUrl in the config file
- Official docs confirm the hosted server uses dynamic client registration by default; the loopback callback (127.0.0.1) has not been tested yet
- Authorization requests only the read scopes listed in the protected-resource metadata (organizations, projects, database, analytics, edge functions, environment); whether the server narrows the token by scope is untested, and without narrowing the token still carries full permissions. The recipe also sets read_only=true (official parameter: queries run as a read-only Postgres user and write tools are not registered)
- Prefer non-production projects; write tools such as migrations and function deploys are unavailable in read-only mode, and the storage feature group is not enabled by default
- Permissions and requirements
- No extra permissions
Network at run time: yes - Data flow
- Connects to the remote service mcp.supabase.com. Credentials are supplied by you inside Teloa and never pass through this site. This site collects no user information.
Entry teloa.mcp-supabase-remote · version 1.0.0