supabase

Sync Supabase projects from the Lovable panel into the OpenClaw MCP registry.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/MindOpsTeam/agente-cfo --skill supabase-mindopsteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/MindOpsTeam/agente-cfo/tree/main/skills/supabase
Command: npx skills add https://github.com/MindOpsTeam/agente-cfo --skill supabase-mindopsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill automates exposing Supabase projects as MCP servers by syncing the panel state with the local OpenClaw MCP registry, eliminating manual provisioning.

Core Features & Use Cases

  • Automatically registers new Supabase projects as MCPs using the render_mcp_config and mcp_manager flow.
  • Removes MCPs for deactivated or removed projects from the Lovable panel.
  • Runs as a daemon on a VPS with a configurable interval and uses PANEL_BASE_URL, PANEL_TOKEN, and HOOKS_TOKEN for authentication.
  • Restarts the OpenClaw gateway when changes occur to apply updates immediately.
  • Integrates with the existing agent scripts to ensure consistent MCP naming and environment propagation.

Quick Start

Install and start the supabase_sync service on your VPS, configure the required environment variables, and let it run to auto-register Supabase MCPs.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I automatically register Supabase projects as MCP servers?

You can automatically register Supabase projects as MCP servers by running a daemon that polls the Lovable panel and syncs active projects directly into the local OpenClaw MCP registry.

What environment variables are required to sync Supabase MCPs with OpenClaw?

Syncing Supabase MCPs with OpenClaw requires configuring three specific environment variables: PANEL_BASE_URL, PANEL_TOKEN, and HOOKS_TOKEN for authenticating the daemon's panel requests.

How does the Supabase MCP registry handle deactivated projects on the Lovable panel?

The Supabase MCP registry automatically removes deactivated or removed projects from the Lovable panel, ensuring the local OpenClaw configuration stays synchronized without manual cleanup.

Do I need a VPS to run the daemon for automating Supabase MCPs?

Yes, you need a VPS to run the daemon, which operates on a configurable polling interval to continuously monitor the Lovable panel and apply Supabase MCP updates.

How are Supabase MCP configuration changes applied immediately in OpenClaw?

Supabase MCP configuration changes are applied immediately by automatically restarting the OpenClaw gateway whenever the daemon detects and registers updates from the Lovable panel.