Give your Supabase app its own MCP server

Supabase introduced an MCP Server block that lets developers expose their application’s actions as Model Context Protocol tools for use in clients such as ChatGPT and Claude, while preserving each customer’s existing Supabase identity and Row Level Security permissions. The generated Edge Function includes MCP handling, OAuth authentication middleware, a caller identity tool, and a structure for registering custom tools, allowing developers to use user-scoped Supabase queries without service role keys. Tools can access databases, Edge Functions, APIs, and external services, but Supabase recommends retaining business rules in shared application logic. A Sizzle demonstration showed customers using MCP to retrieve products and generate video ads directly within an AI conversation, with optional embedded interfaces through MCP Apps that can reuse existing React components. To deploy the feature, developers configure asymmetric signing keys, OAuth 2.1 and dynamic client registration, add a consent page, disable the Edge Function’s built-in JWT check for unauthenticated discovery requests, and connect agents to the deployed server URL.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.