What problem does it solve? Choosing an MCP server for Okta automation is risky because the ecosystem is volatile, the official server is beta and source-only, and Identity Governance coverage is nearly nonexistent. This Skill provides a verified snapshot of every relevant option so you avoid deploying unreviewed or mis-scoped tooling. ## Core Features & Use Cases - Official server assessment: Details the okta/okta-mcp-server tool inventory (users, groups, apps, policies, logs), OAuth 2.0 auth models (Device Authorization Grant and Private Key JWT), stdio transport, and beta/source-only distribution constraints. - Third-party comparison: Covers Tako MCP, kapilduraphe, indranilokg, and StackOne alternatives, plus the single IGA-focused community project (ashwinramn/okta-mcp-em-python) with its SSWS-only auth and narrow CSV/SoD/bundle scope. - Governance gap analysis: Documents the absence of Okta Identity Governance MCP coverage and gives practical guidance on building a small in-house MCP server wrapping OIG REST endpoints. - Use Case: An engineer asked to enable AI-agent automation of Okta access reviews uses this Skill to learn that no production-ready governance MCP exists, then follows the guidance to wrap campaign and access-request endpoints directly. ## Quick Start Ask the AI to compare the official Okta MCP server with third-party alternatives for automating user and group management in your tenant.