Ext Ops Panel
Open dashboard
Comparison

armo-ctrl vs Keycloak Admin

armo-ctrl is a plugin bundle for AI coding tools published by armosec. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Keycloak Admin is an MCP server published by mrz1880. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacearmo-ctrlKeycloak Admin
Claude Code: claude-plugins-community Listed
Version: 0.0.13
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.3
Downloads/month (npm): 281
Downloads/week (npm): 43
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

armo-ctrl vs Keycloak Admin
Factarmo-ctrlKeycloak Admin
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-keycloak-admin)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 2
Hooks it runs (differs)1Not published
Parts of the bundle (differs)15Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/armosec/armoctlgithub.com/mrz1880/mcp-keycloak-admin
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

armo-ctrl

In its own words, on Claude Code: claude-plugins-community:

Drive the ARMO Cloud and Kubernetes security platform from natural language: incidents, CVEs, posture, runtime, and policies, with dry-run safety on every mutation.

Keycloak Admin

In its own words, on Official MCP Registry:

Administer Keycloak via its Admin REST API: users, roles, clients, groups, IdP, events.

How to run each

armo-ctrl As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install armo-ctrl@claude-community

Keycloak Admin As a local MCP server: npm package

Claude Code
claude mcp add --env "AUTH_MODE=<YOUR_AUTH_MODE>" --env "KC_ADMIN_PASSWORD=<YOUR_KC_ADMIN_PASSWORD>" --env "KC_CLIENT_SECRET=<YOUR_KC_CLIENT_SECRET>" --env "KEYCLOAK_BASE_URL=<YOUR_KEYCLOAK_BASE_URL>" --env "KEYCLOAK_REALM=<YOUR_KEYCLOAK_REALM>" --transport stdio mcp-keycloak-admin -- npx -y mcp-keycloak-admin

Requires: AUTH_MODE, KC_ADMIN_PASSWORD (secret), KC_CLIENT_SECRET (secret), KEYCLOAK_BASE_URL, KEYCLOAK_REALM

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of armo-ctrl publish no settings it asks for, so we do not compare settings.

What it can do: armo-ctrl · What it can do: Keycloak Admin · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built