Okta MCP Server

The Okta MCP Server is the official Model Context Protocol implementation maintained by Okta for connecting LLM agents to Okta's Admin Management APIs. It exposes natural language access to identity operations such as creating users, managing groups, listing applications, configuring authentication policies, reviewing system logs, and managing branded sign-in experiences. The server is built on the Okta Python SDK and supports two OAuth 2.0 authentication flows: Device Authorization Grant for interactive sessions and Private Key JWT for browserless or automated use.

A notable design feature is scope-based tool loading: the server reads the OAuth scopes granted at startup (via the OKTA_SCOPES environment variable) and silently disables any tool that lacks the required permissions. This keeps the agent's available capabilities aligned with the principle of least privilege. Destructive actions like deactivating users or deleting policies use the MCP Elicitation API to prompt for confirmation before executing.

Tool coverage spans users, groups, applications, authentication and access policies, device assurance, system logs, brands and themes, custom pages, email templates and settings, custom domains, and email domains, covering most of the day-to-day surface area an Okta admin operates on.

Tools

Prerequisites

• Active Okta org with admin permissions to create app integrations and grant API scopes
• Python 3.8+ or Docker
• uv package manager (if running without Docker)
• An MCP-compatible client (Claude Desktop, etc.)

Create an Okta app integration

Choose one auth flow:

• Device Authorization Grant (interactive): Create an OIDC Native Application, enable the Device Authorization grant type, and grant the API scopes you want to expose.
• Private Key JWT (browserless): Create an API Services app, generate or upload an RSA key pair, grant API scopes, and assign appropriate admin roles. Save the Client ID, Key ID, and private key.

Install

Option A: Docker

git clone https://github.com/okta/okta-mcp-server.git
cd okta-mcp-server
cp .env.example .env
docker-compose up -d

Option B: uv

git clone https://github.com/okta/okta-mcp-server.git
cd okta-mcp-server
uv sync

Claude Desktop config (Docker + Private Key JWT)

{
  "mcpServers": {
    "okta-mcp-server": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "OKTA_ORG_URL",
        "-e", "OKTA_CLIENT_ID",
        "-e", "OKTA_SCOPES",
        "-e", "OKTA_PRIVATE_KEY",
        "-e", "OKTA_KEY_ID",
        "okta-mcp-server"
      ],
      "env": {
        "OKTA_ORG_URL": "https://your-org.okta.com",
        "OKTA_CLIENT_ID": "your-client-id",
        "OKTA_SCOPES": "okta.users.read okta.groups.read",
        "OKTA_PRIVATE_KEY": "-----BEGIN RSA PRIVATE KEY-----\nYour key\n-----END RSA PRIVATE KEY-----",
        "OKTA_KEY_ID": "your-key-id"
      }
    }
  }
}

Claude Desktop config (uv + Device Authorization)

{
  "mcpServers": {
    "okta-mcp-server": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/path/to/okta-mcp-server",
        "okta-mcp-server"
      ],
      "env": {
        "OKTA_ORG_URL": "https://your-org.okta.com",
        "OKTA_CLIENT_ID": "your-client-id",
        "OKTA_SCOPES": "okta.users.read okta.groups.read"
      }
    }
  }
}

Environment variables

• OKTA_ORG_URL: Your Okta org URL (e.g. https://your-org.okta.com)
• OKTA_CLIENT_ID: Client ID of the Okta app integration
• OKTA_SCOPES: Space-separated list of OAuth scopes. Tools are loaded only for scopes granted here.
• OKTA_PRIVATE_KEY: (Private Key JWT only) PEM-formatted RSA private key
• OKTA_KEY_ID: (Private Key JWT only) Key ID for the public key registered in Okta
• OKTA_LOG_LEVEL: Optional. Set to DEBUG for verbose logging.

The server enforces least privilege via scope-based tool loading: any tool whose required scope is not listed in OKTA_SCOPES will not appear to the model.

• Onboard a new hire: create their Okta user, add them to the right groups, and assign apps in one conversation.
• Investigate a security incident by querying the System Log for failed sign-ins, MFA challenges, or admin actions in a time window.
• Audit and clean up: list inactive users, applications without assignments, or groups with stale membership and deactivate them.
• Roll out a new authentication or MFA policy and create the rules that scope it to specific groups or apps.
• Manage branded sign-in experiences by updating brand themes, custom pages, email templates, and verifying custom domains.

• "Create a new user jane.doe@acme.com in Okta and add her to the Engineering and All-Employees groups."
• "Show me all failed login events in the System Log from the last 24 hours grouped by user."
• "List every application in our Okta org that has zero group assignments and deactivate them after confirming."
• "Update the authentication policy for the Salesforce app to require MFA for users outside the office network."
• "Replace the brand theme logo and send a test email using the Welcome email template."

• Officially maintained by Okta, with coverage that tracks the Admin Management APIs closely.
• Scope-based tool loading enforces least privilege automatically based on the OAuth scopes you grant.
• Supports both interactive (Device Authorization) and headless (Private Key JWT) auth flows.
• Confirmation prompts on destructive operations via the MCP Elicitation API reduce the risk of accidental deletes or deactivations.

• Self-hosted only: requires running Docker or a Python environment locally, plus configuring an Okta app integration and scopes before first use.
• Private Key JWT setup involves managing RSA keys and admin role assignments, which is non-trivial for casual users.
• Subject to Okta's per-org API rate limits, which can throttle bulk operations on large tenants.

• Auth0 MCP server for managing Auth0 tenants (Okta's sister identity product).
• Microsoft Entra ID / Graph MCP integrations for managing users, groups, and apps in Azure AD.
• Direct use of the Okta Terraform Provider or the Okta CLI when deterministic, declarative management is preferred over LLM-driven operations.