1
Ability to customize the .well-known/ directory contents
Source: supabase/supabase#43050 · opened by @fzaninotto
I have built an authenticated MCP server based on a Supabase service, leveraging Supabase OAuth. I originally wanted to use Supabase Edge functions for that, but it turns out it's impossible. Since authenticated MCP servers use OAuth, the MCP client must be able to determine the authentication provider for the server by calling the .well-known path on the server. To my knowledge, it is not possible to customize the contents of that resource on a Supabase instance, so I was stuck. I ended up implementing the MCP server in a separate express server, hosted on a domain where I controlled the .well-known contents. This kinds of defeats the purpose of a backend as a service... Anyway, the MCP server is working but it's cumbersome to host (see for a demo of what I built). I wanted to know if there is a new or hidden way to customize the .well-known/ directory contents, or the Supabase team intends to support it in the near future? Because without OAuth, the ability t…
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow Customization of /migrations Directory in config.toml for Supabase Migrations and Shadow Database
7 votes · 0 comments
Enhanced SQL Query Management for Supabase CLI: A Proposal for Query File and Folder Support
4 votes · 0 comments
Add Supabase to Atlassian Statuspage third-party component directory (statuspage.io - monitoring)
2 votes · 0 comments
Separate `docker` directory into a separate repository
1 vote · 0 comments
Multi-project support for self-hosted Supabase Studio
1 vote · 0 comments
No comments yet.