Aliyun RDS Supabase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

create_auth_user

Registers a new user account in Supabase using the Admin API with email and password. Requires service role key for authentication.

Instructions

Creates a new user using Supabase Admin API. Requires service role key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "create_auth_user"
  }
}

Input Schema

Name	Required	Description	Default
`role`	No	User role.	authenticated
`email`	Yes	The email address for the new user.
`password`	Yes	Plain text password (min 6 chars). WARNING: Insecure.
`app_metadata`	No	Optional app metadata.
`user_metadata`	No	Optional user metadata.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jul 14, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses the use of Admin API and the need for a service role key, but with no annotations, more behavioral details (e.g., side effects, authentication status) would be helpful. It provides some transparency but is not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the essential action, and every sentence adds value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given five parameters and no output schema, the description covers the main purpose and prerequisite, but could be more complete regarding return values, error states, or typical usage scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage for parameter descriptions, so the description does not need to add extra meaning. It does not elaborate beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new user via the Supabase Admin API, with a specific verb and resource. It distinguishes from sibling tools like update_auth_user and delete_auth_user.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It mentions the requirement of a service role key, which is a useful prerequisite, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.