Supabase lets your app itself become an MCP server
Supabase's new direction lets your app expose MCP so users can connect ChatGPT or Claude and access their own data as themselves through Auth and RLS.
Your app's MCP server Supabase already had an MCP server for developers. It lets Claude, Cursor or other coding agents work with your Supabase project. Now Supabase is bringing MCP to the other side: your own application can become an MCP server for its users. Instead of a coding agent working on your Supabase project, a user can connect Claude, ChatGPT or Cursor directly to your app: User → Claude / ChatGPT / Cursor → MCP → Your App → Supabase Auth → RLS → User Data The user signs in through the same Supabase Auth flow your app already uses. Every MCP tool call then runs as that user, and your existing Row Level Security policies decide which data the agent can access. So the agent doesn't get general access to your Supabase project. It gets the same access as the user it represents. Your app becomes the MCP server. The agent acts as the user. Auth and RLS remain the security boundary. https://supabase.com/blog/select-2026-build-anything