lovable-deploy

Deploy Lovable backend work via MCP, browser automation, or manual prompts.

20|5|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/10K-Digital/lovable-agent-skills --skill lovable-deploy-10k-digital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lovable-deploy
Source: https://github.com/10K-Digital/lovable-agent-skills/tree/main/plugins/lovable/skills/lovable-deploy
Command: npx skills add https://github.com/10K-Digital/lovable-agent-skills --skill lovable-deploy-10k-digital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying Supabase Edge Functions and database migrations to Lovable projects requires choosing between MCP, browser, and manual transports while respecting authorization rules, credit costs, and verification steps. This Skill encodes that decision logic so agents deploy backend work correctly without wasting Lovable credits or skipping confirmations. ## Core Features & Use Cases - Transport selection: Chooses between browser automation, the official Lovable MCP server, or a manual prompt based on deploy.mode configuration. - YOLO authorization policy: Reads deploy.yolo_mode from .lovable-agent/config.json to determine whether Lovable prompts can be submitted without repeated user confirmation. - Deployment verification: Distinguishes accepted from verified deployments, classifies MCP failures, and falls back to browser inspection instead of charged status prompts. - Use Case: After writing a Supabase Edge Function locally, ask your agent to deploy it; the Skill checks GitHub sync, scans for missing secret names, consolidates operations into one prompt, submits it through the configured transport, and verifies the result. ## Quick Start Deploy my Supabase Edge Function and pending database migrations to my Lovable project using the configured transport.

Frequently Asked Questions about lovable-deploy

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

FAQPage Schema
How do I deploy Supabase Edge Functions to Lovable from my IDE?

Implement and test the function locally, confirm GitHub has the latest commit, then let the agent submit one consolidated operation prompt through the configured transport. Browser automation is preferred, with the official Lovable MCP server as fallback.

What is YOLO mode in Lovable deployment configuration?

YOLO mode is the deploy.yolo_mode setting in .lovable-agent/config.json that grants standing authorization to submit in-scope Lovable prompts without repeated confirmation. When off, the agent must ask before submitting prompts, and destructive database operations always require confirmation.

Should I use Lovable MCP or browser automation for deployment?

Browser automation against the configured Lovable project is tried first; the official Lovable MCP at mcp.lovable.dev is used only when browser submission is unavailable. If neither works, a manual prompt is returned for the user to submit.

Why did my Lovable MCP deployment fail and what happens next?

MCP failures are classified before fallback: unsupported operations, timeouts, or unavailable servers fall back to browser automation, while authentication failures require re-authentication or manual handoff. Authentication failures are never retried indefinitely.

Can I deploy database migrations without confirming every time?

With deploy.confirm_migrations set to false (the default), ordinary in-scope migrations need no repeated approval when YOLO is on. Setting it to true requires confirmation for migration execution, and destructive or irreversible operations always require confirmation.