keycloak-dev-kit
v0.1.0Keycloak 26.x extension (provider JAR) development - SPI catalog grounded in the target tag's source, Maven packaging and shading, Docker dev environment (start-dev, reverse proxy, two-node cluster), real verification, pitfalls, and turning a fork/PR into a plugin (keycloak-provider-dev)
By Alfredo Oliviero0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install keycloak-dev-kit for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install keycloak-dev-kit@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/primax79/agentic-coding-kitClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/keycloak-dev-kit/.
Plugin files
├── .claude-plugin/plugin.json└── skills/keycloak-provider-dev/SKILL.md
Included Skills1
Use when writing, building, testing or reviewing a Keycloak (Quarkus distribution, 26.x) extension - a provider JAR implementing Keycloak SPIs (well-known endpoints, realm/admin REST resources, key providers, client registration policies, scheduled tasks, identity providers, authenticators) - or when deciding whether a Keycloak fork/PR can be turned into a plugin. Covers grounding claims in the Keycloak source of the exact target tag, the Maven packaging (provided deps, shading, META-INF/services), a Docker dev environment (start-dev, reverse proxy, two-node cluster), verification that the provider is really loaded, and known pitfalls. Not for configuring Keycloak as a user (realms, clients, themes only).
Plugin manifests1
{
"name": "keycloak-dev-kit",
"version": "0.1.0",
"description": "Keycloak 26.x extension (provider JAR) development - SPI catalog grounded in the target tag's source, Maven packaging and shading, Docker dev environment (start-dev, reverse proxy, two-node cluster), real verification, pitfalls, and turning a fork/PR into a plugin (keycloak-provider-dev)",
"author": {
"name": "Alfredo Oliviero"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[keycloak-dev-kit on Agent Plugins Marketplace](https://pluginsmp.com/plugins/keycloak-dev-kit)