keycloak-mcp-server

manage-user-groups

Add or remove users from groups in Keycloak realms. Specify realm, user ID, group ID, and action to manage group membership.

Instructions

Add or remove users from groups

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>",
      "userId": "<userId>",
      "groupId": "<groupId>",
      "action": "<action>"
    },
    "name": "manage-user-groups"
  }
}

Input Schema

Name	Required	Description
`realm`	Yes	Realm name
`action`	Yes	Action to perform
`userId`	Yes	User ID
`groupId`	Yes	Group ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

There are no annotations, so the description must carry the full behavioral burden. It only states that it adds/removes users, but does not disclose side effects, permission requirements, idempotency, or failure modes. This is insufficient for a state-changing operation.

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 sentence that delivers the core purpose without any filler. It is perfectly concise and easy to parse.

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?

Given the absence of annotations and an output schema, the description should provide more context about invocation outcomes, errors, or conditions. The minimal text leaves gaps that could lead to incorrect usage or expectations.

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% description coverage for all four parameters, including an enum for 'action'. The description adds no extra semantic meaning beyond what the schema already provides, warranting the baseline score.

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 specific verbs 'Add or remove' and clearly identifies the resource ('users from groups'), making its function unambiguous. It distinguishes itself from sibling tools like create-group or assign-role-to-group, which handle different operations.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as assign-role-to-group or create-group. The description lacks any context about prerequisites, exclusions, or preferred scenarios.

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

Deploy Server