keycloak-mcp-server

create-client

Register a new client or application in a Keycloak realm. Specify realm and client ID, plus optional redirect URIs, public client flag, and enabled status.

Instructions

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>",
      "clientId": "<clientId>"
    },
    "name": "create-client"
  }
}

Input Schema

Name	Required	Description
`name`	No	Client name
`realm`	Yes	Realm name
`enabled`	No	Enabled status
`clientId`	Yes	Client ID
`description`	No	Client description
`publicClient`	No	Public client
`redirectUris`	No	Redirect URIs

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 full responsibility for disclosing behavioral traits. It only states the action ('Register') without mentioning permissions, idempotency, side effects, or error behavior. For a mutation tool, this lack of detail leaves significant gaps.

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, front-loaded sentence that states the essential purpose without extraneous words. It is concise and well-structured, making it 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?

Despite a rich schema (7 params), there is no output schema and no annotations. The description only covers the basic creation action, omitting details like prerequisites, idempotency, return values, or potential errors. For a create operation with moderate complexity, this is inadequate for full contextual completeness.

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 provides descriptions for all 7 parameters, giving 100% coverage. The tool description adds no additional parameter-level context beyond 'client/application in a realm', so it neither compensates for nor detracts from the schema's already sufficient parameter documentation.

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 the specific verb 'Register' and identifies the resource as 'client/application in a realm', clearly distinguishing it from siblings like update-client, delete-client, and list-clients. It unambiguously states the tool's function.

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 the tool is for creating clients, but it does not explicitly state when to use it vs. alternatives such as update-client or list-clients. No exclusions or alternative tool references are provided, so guidance is only implied by the verb 'Register'.

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

Deploy Server