Use Okta’s self-hosted MCP server for permission-scoped identity administration. Compare OAuth scopes, account access and supported management tools.
Okta’s self-hosted MCP server connects an assistant to supported Okta management operations. It is a separate first-party implementation from community Okta connectors. The current README describes scope-based tool loading, so an account’s configured scopes affect which tools the assistant can see.
Select the intended Okta organisation and identify the user, group or application involved in the question. Inspect the current record before proposing an administrative change. Keep identifiers in the explanation so similarly named accounts or groups are not confused.
The project documents Docker and Python distribution options, including the okta-mcp-server package. Follow its current OAuth application, organisation URL and scope instructions, including signing-key configuration where required. A successful login to Okta for another service does not provide the administrative capabilities of this server.
Maintainer’s setup and tool reference. Browse identity access MCP servers for related workflows.
The Okta OAuth application, organisation URL, scopes and credential configuration documented by Okta.
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Manage Authentik through AI assistants
A collection of Model Context Protocol (MCP) servers for Authentik API integration, available in both Python and Node.js implementations.
integration that connects BloodHound with AI through MCP, allowing security professionals to analyze Active Directory attack paths using natural
MCP server for CyberQP's privileged access management API.
MCP server for Microsoft Entra ID sign-in and audit-log triage (read-only)