feat: self-hosted supabase stack #92
Draft
+970
−36
Conversation
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
This was referenced Jun 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
WIP.
This allows you to connect MCP to your local Supabase stack. The platform abstraction work simplified what was required to make this possible.
We use the
/api/platformAPI shims in the studio container to implement the majority of this. Some tools will not be possible locally, like account level operations and branching, so we need to add logic to conditionally omit those tools instead of throwing anot implementedexception.The biggest unknowns right now are migration and edge function tools, since both of these require access to the supabase CLI to implement correctly.
Ref: AI-101