Skip to main content

Configure Supabase for the AI Gateway

To allow your users to securely query projects, databases, and Edge Functions using their AI clients, you can configure the Supabase Model Context Protocol (MCP) server within the JumpCloud AI Gateway.

Prerequisites​

  • Before configuring specific enterprise applications, we recommend reviewing the Get Started: AI Gateway guide to familiarize yourself with the gateway architecture and core AI concepts (such as MCP servers and AI clients).

Completing Application Setup​

Before you can connect this server to the AI Gateway, you must determine your authentication method. See Supabase’s Supabase MCP Server to learn more.

  • OAuth: Supabase’s hosted MCP server supports OAuth Dynamic Client Registration (DCR). No app creation or Personal Access Token is required for interactive use.
  • API Token: Use a Supabase Personal Access Token (PAT) when browser-based OAuth is not possible, such as CI environments. See Supabase’s CI environment to learn more.
Important

Connecting an AI client to production Supabase projects carries security risks. Prefer project scoping and read-only mode when possible, and review Supabase’s security guidance before enabling write tools.

Configuring the Server in JumpCloud​

See Adding MCP Servers in Configure AI Gateway Integrations and use the following values to configure this server:

  • App: Select Supabase (if you have an existing SSO application or bookmark), or + Add App to create it
  • Name: Enter a name, for example Supabase
  • Prefix: Enter a value to prepend to MCP tool names
    • Note: Prefixes must be unique. Maximum 8 characters, letters and numbers only
  • URL: https://mcp.supabase.com/mcp
    • Note: You can append query parameters to scope access. For example, ?project_ref=<project-ref>&read_only=true limits tools to a single project and read-only SQL. See Supabase’s configuration options for features, project_ref, and read_only.
  • MCP authentication method: Select OAuth or API
    • Note: Select API when connecting from a CI environment that requires a Supabase Personal Access Token (PAT)
  • Advanced fields: Not required
  • App API documentation link (API only): Enter https://supabase.com/docs/guides/getting-started/mcp#ci-environment

Your users will now see Supabase listed as an available application when they authenticate their AI clients through the JumpCloud AI Gateway. When prompted for API authentication, users can click the documentation link you provided to learn how to generate a Supabase Personal Access Token.

Was this information helpful?