Skip to main content
Glama
ni-c

wikijs-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a user

create_user

Create a user account in Wiki.js with email, name, optional group IDs, and either a password or a welcome email invitation so new users can log in and access permitted content.

Instructions

Creates an account. For a local account supply a password, or set send_welcome_email so Wiki.js mails an invitation instead. Groups are given by id — list_groups has them, and an account in no group can log in but see nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name.
emailYesEmail address, which is also the login for local accounts.
groupsNoGroup ids to put the account in.
passwordNoInitial password for a local account. Never echoed back by this server.
provider_keyNoAuthentication provider (default "local").
confirm_tokenNoToken from this tool’s previous, unconfirmed call. Omit it to receive one.
send_welcome_emailNo
must_change_passwordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / groups / items / maximum
      Previous value: -9007199254740991New value: +2147483647
  2. Changed2 schema fields changedv0.2.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when the answer was shortened to fit the budget.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read/write and idempotency hints. The description adds useful behavioral consequences: sending an invitation email and the fact that a no-group account can log in but sees nothing. No contradiction with the annotations.

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?

Three sentences, no wasted words, and the main purpose is stated first. Each sentence adds operational value: authentication choice, group id sourcing, and groupless behavior.

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?

For an 8-parameter creation tool with an output schema, the description covers the key decision points and group behavior. It omits only the must_change_password semantics, which is a minor gap given the schema explains most other parameters.

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

Parameters4/5

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

Schema coverage is 75%, and the description adds meaning for send_welcome_email (mail an invitation), password (local-account path), and groups (ids from list_groups, with visibility consequence). It does not clarify must_change_password, which the schema also leaves undescribed.

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

Purpose4/5

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

"Creates an account" names the action and resource clearly. It is not a tautology, but it does not explicitly differentiate from sibling create_* tools; the title and resource name make that differentiation easy.

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

Usage Guidelines5/5

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

The description states the two local-account authentication paths (password vs send_welcome_email) and names list_groups as the source for group ids. It also explains the consequence of omitting groups, which tells an agent when groups are needed.

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

Deploy Server

Other Tools