Ability to customize the .well-known/ directory contents

by Francois Zaninotto

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 https://marmelab.com/atomic-crm/doc/users/mcp-server/ 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?

OP

Francois Zaninotto·2/20/2026, 2:17:01 PM

How to help

Francois Zaninotto is seeking a way to customize the .well-known directory contents on a Supabase instance to support an authenticated MCP server using OAuth. Currently, he had to implement the server on a separate Express server due to this limitation. He inquires if there is a way to achieve this on Supabase or if future support is planned.

Product areas

Edge Functions

Auth

Stack

Express

Help on GitHub

github·12d ago

Help on GitHub

Ability to customize the .well-known/ directory contents

by Francois Zaninotto

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 https://marmelab.com/atomic-crm/doc/users/mcp-server/ 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?

OP

Francois Zaninotto·2/20/2026, 2:17:01 PM

How to help

Francois Zaninotto is seeking a way to customize the .well-known directory contents on a Supabase instance to support an authenticated MCP server using OAuth. Currently, he had to implement the server on a separate Express server due to this limitation. He inquires if there is a way to achieve this on Supabase or if future support is planned.