Identity AIops MCP server

<!-- mcp-name: io.github.AIops-tools/identity-aiops -->

Identity AIops

Governed AI-ops for self-hosted identity providers — Keycloak + authentik.

identity-aiops gives AI agents (and the humans supervising them) a safe, audited way to operate the identity plane of self-built and small/mid-size infrastructure: who can sign in, what failed and why, which OAuth clients are misconfigured, and who still has no second factor. It is built for teams running their own Keycloak or authentik who want agent-driven identity operations with receipts — every tool call is audited, and writes carry risk-tier labels with dry-run previews and undo tokens.

Verification status: modelled on the public Keycloak admin REST API and

authentik API v3 and exercised against mocked responses; there is no recorded

end-to-end run against a live instance yet. identity-aiops doctor is the

fastest live check — see docs/VERIFICATION.md.

What it does

29 MCP tools: 21 reads (including the 4 analyses) + 6 governed writes + 2 undo tools (undolist, undoapply). The same tools work on both platforms — a per-target platform field selects the API shape (auth flow + resource paths).

Supported platforms

Platform notes: requirepasswordreset, rotateclientsecret, clientsessions, clientsessionstats, and userlockout_status are Keycloak-shaped (authentik has no equivalent endpoint — the tools return a teaching error there). authentik contributes the global session list used by the stale-access audit's orphaned-session check.

Missing a platform (Authelia, Zitadel, Ory...), an endpoint, or an analysis you need? 缺功能提 issue/PR 欢迎留言 — open an issue or PR at https://github.com/AIops-tools/Identity-AIops, feature requests welcome.

What this tool does, and does not, decide

It delivers identity-provider operations — reads and writes — accurately and records every one of them. It does not decide whether a write is allowed to happen. That is the agent's judgement, or the permission of the account you connect it with: give the Keycloak service account (or authentik token) only the roles you want the agent to have — view-users / view-events / view-clients and no manage-* — and the writes fail at the server, the place that actually owns the permission.

Shortened. The full README is on GitHub.