supabase

Call Supabase Management and PostgREST APIs directly via HTTP.

8|1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mnlt/teleport --skill supabase-mnlt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/mnlt/teleport/tree/main/skills/supabase
Command: npx skills add https://github.com/mnlt/teleport --skill supabase-mnlt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supabase exposes two REST surfaces (Management API and per-project REST) that developers often access through MCP servers or ad-hoc tooling. This Skill provides direct, credential-safe HTTP access to Supabase APIs, reducing context size and complexity when building AI-assisted workflows.

Core Features & Use Cases

  • Two-surface API split: Management API for organization-level tasks and per-project REST endpoints for database, auth, storage, and real-time actions.
  • Credential management via environment variables: SUPABASE_ACCESS_TOKEN for management tasks, SUPABASE_URL with SUPABASE_ANON_KEY or SUPABASE_SERVICE_ROLE_KEY for per-project REST, ensuring secrets are kept out of transcripts.
  • Use cases include listing projects and API keys, creating or updating records in public schemas, and performing admin or project-scoped operations directly from the agent.

Quick Start

Provide your SUPABASE_URL and credentials and tell me the task (management or per-project REST) to begin.

Frequently Asked Questions about supabase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I call Supabase REST APIs directly from an AI agent without an MCP server?

You can call Supabase REST APIs directly by routing HTTP requests from the agent to the Management API or per-project PostgREST endpoints, using environment variables for credentials to keep secrets out of transcripts.

What credentials do I need to query a Supabase database via REST from an agent?

To query a Supabase database via REST, you need to set the SUPABASE_URL environment variable alongside either the SUPABASE_ANON_KEY or SUPABASE_SERVICE_ROLE_KEY to authenticate per-project requests.

Can I manage my Supabase projects and fetch API keys using REST endpoints?

Yes, you can perform organization-level admin tasks such as listing projects and fetching API keys by authenticating with the SUPABASE_ACCESS_TOKEN against the Supabase Management API.

What is the difference between the Supabase Management API and per-project REST surfaces?

The Supabase Management API handles organization-level admin tasks using an access token, while per-project REST endpoints interact directly with database, auth, and storage data using project URLs and anon or service role keys.

Does this approach to Supabase API access keep credentials out of chat transcripts?

Yes, this approach requires credentials via environment variables like SUPABASE_ACCESS_TOKEN and SUPABASE_ANON_KEY, ensuring secrets are passed securely for host routing without appearing in agent transcripts.

Why use direct HTTP calls to Supabase instead of a central MCP server?

Using direct HTTP calls to Supabase REST surfaces reduces context size and complexity when building AI-assisted workflows, bypassing the overhead of routing requests through a central MCP server.