Repository navigation
fix(mcp): use native HTTP for Devin MCP connections - #51646
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@playb0t is attempting to deploy a commit to the Supabase Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Rodriguespn
left a comment
There was a problem hiding this comment.
Thanks for the contribution, @playb0t! The move off mcp-remote is the right path forward. Devin (prev Windsurf) didn't support remote MCP servers, so we were using mcp-remote npm package as a proxy. It's not the case anymore.
I tested it locally with Devin CLI 3000.11.3:
devin mcp add -s user supabase "https://mcp.supabase.com/mcp"writesthe~/.config/devin/mcp_config.json` file.- The Supabase OAuth flow completed in the browser.
project_ref,read_onlyandfeaturesare kept in the stored URL.- The local URL (
localhost:54321) is written without an auth prompt.
I've left a few inline comments, mainly to keep the change aligned with how the other clients are set up (cleanup, ordering, test scope and a couple of copy tweaks). Requesting changes for those; happy to approve once they're in.
|
Thanks for running the hosted flow, that was the one check I could not do from here. Pushed a second commit with all of it: |
Rodriguespn
left a comment
There was a problem hiding this comment.
Thank you for addressing my comments @playb0t. Preview looks good. Approving this. Thanks again for your contribution!
kemaldotearth
left a comment
There was a problem hiding this comment.
Confirmed via local build of docs.
db7c184 to
062a6c7
Compare
Braintrust eval report
|

Problem
The Devin Desktop preset wraps Supabase MCP URLs in
npx -y mcp-remote, although Devin Local and Devin CLI support Streamable HTTP natively. Connecting therefore adds a Node/npm bridge that the client does not need. The preset also lacks Devin-specific setup and authentication instructions.Solution
Use the existing native
urlconfiguration for Devin:{ "mcpServers": { "supabase": { "url": "https://mcp.supabase.com/mcp" } } }The generated URL retains the selected project, read-only mode, and features. The internal
windsurfkey is preserved.Add shared setup instructions for the configuration panel and generated Markdown: user-scope installation, the Windows config file location next to the shared macOS/Linux one, a re-authentication command for hosted connections, and loading tools in a new Devin Local or CLI session. Local connections omit the re-authentication step.
Include Devin in the shared client URL round-trip test. The Devin-only test files from the first revision were removed in review so that tests stay shared across clients.
Native configuration follows the official Devin MCP documentation and Devin Local integration.
Validation
ui-patternstest files on the current revision; 34 of them in the MCP section.git diff --checkpassed.Connectedand the fixture tool. Itstools/listrequest came from the bundled Devin Local process.OAuth validation used controlled local fixtures; live Supabase Hosted authorization was not exercised. The full monorepo application build was not run.
Review instructions
pnpm --filter ui-patterns exec vitest run src/McpUrlBuilderandpnpm --filter ui-patterns typecheck.urland preserves the selected project, read-only mode, and features.Checklist
/write-the-docsor/edit-the-docsskill, which applies the docs style guide. N/A: no docs topic edited; the change is in the shared MCP configuration component and its generated instructions.