Okta MCP Server
Connects AI assistants to the Okta API, providing 69+ tools for managing users, groups, applications, policies, group rules, and system logs. Supports user lifecycle management, bulk group membership automation, app provisioning (including AWS IAM roles), policy and rule administration, and audit log queries, with built-in safety guardrails like dry-run defaults, confirmation flags, safety caps, and a read-only mode.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Okta MCP Server
A production-grade Model Context Protocol (MCP) server that connects AI assistants like Claude Desktop, Cursor, and Claude Code to the Okta API.
Empower your LLMs to automate user provisioning, audit group memberships, troubleshoot access policies, query system logs, and inspect applications with built-in safety guardrails.
โจ Features
69+ Okta Tools: Full coverage across Users, Groups, Applications, Policies, Group Rules, and System Logs.
Dual Authentication:
API Token (SSWS): Simple 30-second setup for individual developers and desktop AI clients.
OAuth 2.0 Private Key JWT: Enterprise-grade service app authentication with automatic token rotation.
Built-In Safety Guardrails:
Dry-run by default: All bulk operations and attribute-based assignments preview changes before execution.
Confirmation flags: Single-target destructive actions (deactivation, deletion, MFA reset) require explicit
confirm_*confirmation.Safety caps: Prevents accidental mass updates (capped by default to 50 users unless explicitly overridden).
Flexible Modes:
Full Admin Mode: Full read/write management across all tools.
Read-Only Mode: Safety-first mode that only exposes inspection and search tools (
OKTA_READ_ONLY=true).
Standard I/O (
stdio) & HTTP/SSE: Runs natively as a subprocess inside your AI editor, or as a standalone container.
Related MCP server: TAKO MCP Server for Okta
๐ Quick Start
The fastest way to use Okta MCP server is with uv / uvx without needing to install anything permanently.
1. Claude Desktop
Add the following to your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"okta": {
"command": "uvx",
"args": ["okta-mcp-server"],
"env": {
"OKTA_API_BASE_URL": "https://your-org.okta.com",
"OKTA_API_TOKEN": "00your_okta_api_token"
}
}
}
}2. Cursor
Add to .cursor/mcp.json in your project or global Cursor settings:
{
"mcpServers": {
"okta": {
"command": "uvx",
"args": ["okta-mcp-server"],
"env": {
"OKTA_API_BASE_URL": "https://your-org.okta.com",
"OKTA_API_TOKEN": "00your_okta_api_token"
}
}
}
}3. Claude Code CLI
Add Okta MCP server directly using the Claude Code CLI:
claude mcp add okta -- uvx okta-mcp-server \
-e OKTA_API_BASE_URL="https://your-org.okta.com" \
-e OKTA_API_TOKEN="00your_okta_api_token"๐ Authentication
Method A: API Token (SSWS) โ Recommended for Personal Use
Log in to your Okta Admin Console.
Navigate to Security โ API โ Tokens.
Click Create Token, name it (e.g.
claude-okta-mcp), and copy the generated token.Set the environment variables:
OKTA_API_BASE_URL=https://your-org.okta.com OKTA_API_TOKEN=00your_api_token_here
Method B: OAuth 2.0 Private Key JWT โ For Teams & Enterprise
For zero static secrets, Okta supports service app authentication using public/private key pairs:
In Okta Admin Console, go to Applications โ Applications โ Create App Integration.
Select API Services and create an app.
Under General โ Client Credentials, add a Public Key (PEM) and keep your private key (
private_key.pem).Under Okta API Scopes, grant the desired scopes (e.g.,
okta.users.manage,okta.groups.manage,okta.apps.read).Configure your environment:
OKTA_API_BASE_URL=https://your-org.okta.com OKTA_CLIENT_ID=0oayourclientid OKTA_PRIVATE_KEY_PATH=/path/to/private_key.pem OKTA_SCOPES="okta.users.manage okta.groups.manage okta.apps.manage okta.policies.manage okta.logs.read"
๐ก๏ธ Read-Only Mode
If you want your AI assistant to only inspect, audit, and troubleshoot without making any modifications:
Set OKTA_READ_ONLY=true:
{
"mcpServers": {
"okta": {
"command": "uvx",
"args": ["okta-mcp-server"],
"env": {
"OKTA_API_BASE_URL": "https://your-org.okta.com",
"OKTA_API_TOKEN": "00your_okta_api_token",
"OKTA_READ_ONLY": "true"
}
}
}
}In read-only mode, all 44 state-mutating tools (create_*, update_*, delete_*, assign_*, deactivate_*) are disabled, and only the 25 inspection tools (get_*, list_*, search_*, find_*) are registered.
๐งฐ Available Tools Summary
Category | Tools | Capabilities |
Users |
| Full user lifecycle, profile updates, credential resets, and fuzzy search |
Groups |
| Group administration, bulk membership automation, attribute matching |
Applications |
| SAML/OIDC/Bookmark apps, AWS IAM role assignments, bulk user provisioning |
Policies |
| Sign-on, MFA, Password, and Access policies |
Group Rules |
| Dynamic, rule-based group membership automation |
System Logs |
| Real-time Okta audit log queries with filtering and time windows |
๐ณ Docker Usage
A lightweight multi-platform Dockerfile is included:
docker build -t okta-mcp-server .Running stdio in Docker:
docker run -i --rm \
-e OKTA_API_BASE_URL="https://your-org.okta.com" \
-e OKTA_API_TOKEN="00your_token" \
okta-mcp-serverRunning as an HTTP / SSE Server:
docker run -d --name okta-mcp \
-p 8000:8000 \
-e MCP_TRANSPORT="sse" \
-e MCP_HOST="0.0.0.0" \
-e MCP_PORT="8000" \
-e OKTA_API_BASE_URL="https://your-org.okta.com" \
-e OKTA_API_TOKEN="00your_token" \
okta-mcp-server๐งช Development & Testing
Clone the repository and install dependencies with uv:
git clone https://github.com/csenguttuvan/okta-mcp-server.git
cd okta-mcp-server
uv sync
# Run the test suite
uv run pytest -v
# Run lint and code checks
uv run ruff check .
uv run ruff format --check .๐ License
This project is licensed under the MIT License.
This server cannot be deployed
Maintenance
Related MCP Connectors
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Runtime permission, approval, and audit layer for AI agent tool execution.
Context and control for any AI. Agent identity, scoped access, and proof across tools.
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceEnables LLM agents to manage Okta organizations through natural language, providing full CRUD operations for users, groups, applications, policies, and system logs via Okta's Admin Management APIs.958 PyPI76Apache 2.0- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely query and manage Okta resources for IAM and security administration. It supports dual-mode operation for standard tool interaction or autonomous agent workflows with sandboxed code execution.5-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely access Okta Identity Governance APIs for managing users, groups, apps, access requests, and certifications with configurable deployment modes and safety controls.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Okta users, groups, applications, policies, and logs through natural language commands.Apache 2.0