Skip to main content
Supabase Edge Functions use the generic edge runtime with co-located static assets pattern. The function itself receives all MCP requests through server.fetch; generated View files are bundled alongside it with static_files and served only under the _mcp-use asset subtree. Start from the Supabase deployment example. It packages the files without Docker, a Storage bucket, project configuration mutation, or interactive script.
The command builds .mcp-use/build/views/, stages it beneath the function, and uses Supabase’s static_files configuration to bundle it. The function maps /functions/v1/mcp/_mcp-use/* to that generated tree and forwards every other request to server.fetch. Verify the actual View after deploying:
The deployment uses Supabase CLI’s API deployment mode, so Docker is not a prerequisite. The static file configuration requires a current Supabase CLI.