fix(supabase): add provisioning gotchas and migration filename note#80
Open
ebeprstudios wants to merge 1 commit into
Open
Conversation
Two additions surfaced during a real session setting up a new project via MCP end-to-end. Documented at issue supabase#79. 1. New "Provisioning Projects" section between "Supabase MCP Server" and "Supabase Documentation". Covers: - Free-tier 2-active-project cap, with paused projects counting toward the limit - No delete_project tool in MCP — dashboard-only - Cost confirmation IDs invalidating when the cost changes mid-flow (e.g., org upgrade between confirm_cost and create_project) 2. Migration filename convention paragraph in "Making and Committing Schema Changes". MCP apply_migration timestamps each version; repos that use a manual 001_*.sql prefix will silently diverge from the server-recorded versions, which breaks supabase db push/pull later. Closes supabase#79
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two additions to
skills/supabase/SKILL.mdsurfaced during a real session setting up a new project via the Supabase MCP end-to-end. Both were gaps that cost real round-trips with the user. Full context in #79.Changes
New
## Provisioning Projectssection between## Supabase MCP Serverand## Supabase Documentation. Covers:delete_projectis not exposed via MCP — dashboard-onlyconfirm_costandcreate_project)Migration filename convention paragraph in
## Making and Committing Schema Changes. MCPapply_migrationtimestamps each version (YYYYMMDDHHMMSS_name); repos using a manual001_*.sqlprefix silently diverge from server-recorded versions, breakingsupabase db push/pulllater.Test plan
pnpm test)Closes #79