pocketbase-mcp

Create superuser

create_superuser

Create a superuser account with full administrative access to a PocketBase instance by providing an email and password. This grants complete admin control for managing the backend.

Instructions

Create a new superuser (admin) account. Provide email and password. The new superuser has full administrative access to the instance.

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_superuser"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Superuser email.
`password`	Yes	Superuser password (min 8 chars).
`passwordConfirm`	No	Password confirmation (defaults to password).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds a meaningful behavioral detail: the new superuser gets full administrative access. However, it does not disclose side effects like email uniqueness, verification requirements, or reversibility.

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?

Two concise sentences with no filler. The action, resource, and key consequence are front-loaded, and every sentence contributes real information.

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

Completeness4/5

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

The description covers the core purpose and the principal side effect (full admin access), which is sufficient for a simple creation tool. Minor gaps like duplicate email handling or confirmation flow are not addressed, but the schema covers parameter details and no output schema needs explanation.

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?

Schema description coverage is 100%, with each parameter already documented (email, password with minLength, passwordConfirm with default). The description only repeats that email and password are required, adding no new semantic details beyond the schema.

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?

States a specific verb ('Create') and resource ('superuser (admin) account'), and adds that the account has full administrative access. This clearly distinguishes it from siblings like list_superusers, update_superuser, and delete_superuser.

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?

The description implies when to use it (when creating a new superuser), but it does not explicitly mention alternatives, exclusions, or any prerequisites such as existing admin authentication. Usage context is mostly derived from the verb and resource.

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

Deploy Server