keycloak-mcp-server

create-protocol-mapper

Create a Keycloak protocol mapper to configure JWT organization claims for a client.

Instructions

Create a protocol mapper for a client (CRITICAL for JWT organization claims)

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": "<name>",
      "protocol": "<protocol>",
      "protocolMapper": "<protocolMapper>"
    },
    "name": "create-protocol-mapper"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Protocol mapper name
`realm`	Yes	Realm name
`config`	No	Protocol mapper configuration
`clientId`	Yes	Client ID
`protocol`	Yes	Protocol (e.g., openid-connect)
`protocolMapper`	Yes	Protocol mapper type (e.g., oidc-group-membership-mapper)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and a vague 'CRITICAL' note, but does not disclose side effects (e.g., token impact), permissions required, or whether existing mappers are overwritten. This is insufficient for a creation 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 with a parenthetical emphasis note. It is concise and front-loaded with the essential action, earning its place without clutter.

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 complexity (6 parameters, nested config object, no output schema), the description is incomplete. It does not hint at return values, the expected structure of 'config', or any prerequisites for the protocol mapper. The 'CRITICAL' note is vague and does not compensate for these gaps.

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 coverage is 100% (each parameter has a description), so the baseline is 3. The description does not add extra semantic detail beyond the schema; config is only named as 'Protocol mapper configuration' without further elaboration, but the schema itself covers the basic meaning.

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 clearly states the action (create) and resource (protocol mapper for a client), using a specific verb and object. It distinguishes from related sibling tools like create-client-scope-protocol-mapper by specifying 'for a client'.

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

Usage Guidelines4/5

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

The phrase 'for a client' provides clear context that this is the client-level mapper creation tool, distinguishing it from client-scope mappers. The 'CRITICAL for JWT organization claims' hint gives a use case, though no explicit alternatives or exclusions are listed.

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

Deploy Server