keycloak-mcp-server

create-user

Create a new user in a specific Keycloak realm by supplying realm, username, email, first name, and last name.

Instructions

Create a new user in a specific realm

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": {
      "realm": "<realm>",
      "username": "<username>",
      "email": "<email>",
      "firstName": "<firstName>",
      "lastName": "<lastName>"
    },
    "name": "create-user"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Email address
`realm`	Yes	Realm name
`lastName`	Yes	Last name
`username`	Yes	Username
`firstName`	Yes	First name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the action and scope, but doesn't mention required permissions, potential conflicts (e.g., duplicate username), or what happens on error. This is insufficient for a mutation tool.

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 a single, focused sentence with no filler words, making it easy to parse quickly. It avoids redundancy and is appropriately front-loaded.

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

Completeness2/5

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

The description is too terse for a 5-parameter create operation with no annotations or output schema. It lacks critical context like whether realm must exist, whether duplicate usernames are rejected, or what the response contains.

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 schema already covers all 5 parameters with short descriptions, so the baseline is 3. The description adds no additional parameter semantics—it merely mentions 'specific realm' which maps directly to the realm parameter.

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 uses a specific verb ('Create') and resource ('user') plus a scope ('in a specific realm'), clearly distinguishing it from siblings like update-user, delete-user, and list-users. It leaves no ambiguity about what the tool does.

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 usage for creating a user within a realm but doesn't explicitly state when to use it instead of related tools, nor does it mention prerequisites like the realm needing to exist. The context is clear but not fully developed.

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

Deploy Server