Okta MCP Server

Released Feb 4, 2026

8 views

Apache-2.0

Summary

Okta's official open-source MCP server: manage users, groups, apps, policies and branding in your Okta org from an AI agent, with scope-gated tools and confirmation on destructive actions.

Features

Full CRUD over users, groups, applications and policies via Okta's Admin Management APIs
Scope-based tool loading — only tools covered by OKTA_SCOPES are registered, cutting token use and enforcing least privilege
Destructive operations prompt for confirmation through the MCP Elicitation API, with fallback for clients that lack it
Device Assurance Policy tools for reading, configuring and evaluating device posture
Customisation tools for brands, themes, custom domains, sign-in pages and email templates
Two auth modes: Device Authorization Grant for interactive use, Private Key JWT for server-to-server

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

Open your agent's MCP configuration file.
Merge the snippet below into it, filling in the environment variables with your own values.
Restart the agent — the "Okta MCP Server" tools will be available.

{
  "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 private key content here\\n-----END RSA PRIVATE KEY-----",
        "OKTA_KEY_ID": "your-key-id"
      }
    }
  }
}

Claude Code

Add the server with a single CLI command.

claude mcp add okta-mcp-server -e OKTA_ORG_URL=https://your-org.okta.com -e OKTA_CLIENT_ID=your-client-id -e OKTA_SCOPES=okta.users.read okta.groups.read -e OKTA_PRIVATE_KEY=-----BEGIN RSA PRIVATE KEY-----\nYour private key content here\n-----END RSA PRIVATE KEY----- -e OKTA_KEY_ID=your-key-id -- docker 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

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config).

{
  "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 private key content here\\n-----END RSA PRIVATE KEY-----",
        "OKTA_KEY_ID": "your-key-id"
      }
    }
  }
}

VS Code

Use VS Code promptString inputs for OKTA_ORG_URL, OKTA_CLIENT_ID, OKTA_SCOPES, OKTA_PRIVATE_KEY and OKTA_KEY_ID.

{
  "command": "docker",
  "args": [
    "run",
    "-i",
    "--rm",
    "-e",
    "OKTA_ORG_URL=${input:OKTA_ORG_URL}",
    "-e",
    "OKTA_CLIENT_ID=${input:OKTA_CLIENT_ID}",
    "-e",
    "OKTA_SCOPES=${input:OKTA_SCOPES}",
    "-e",
    "OKTA_PRIVATE_KEY=${input:OKTA_PRIVATE_KEY}",
    "-e",
    "OKTA_KEY_ID=${input:OKTA_KEY_ID}",
    "okta-mcp-server"
  ]
}

Device Authorization Grant via Docker. The volume persists tokens across restarts; copy the auth URL out of `docker logs okta-mcp-server` and open it manually.

{
  "command": "docker",
  "args": [
    "run",
    "-i",
    "--rm",
    "-v",
    "okta-keyring:/home/appuser/.local/share/python_keyring",
    "-e",
    "OKTA_ORG_URL",
    "-e",
    "OKTA_CLIENT_ID",
    "-e",
    "OKTA_SCOPES",
    "-e",
    "PYTHON_KEYRING_BACKEND=keyrings.alt.file.PlaintextKeyring",
    "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"
  }
}

docker-compose variant; reads credentials from a .env file created from .env.example.

{
  "command": "docker-compose",
  "args": [
    "-f",
    "/path/to/okta-mcp-server/docker-compose.yml",
    "run",
    "--rm",
    "okta-mcp-server"
  ]
}

Description

The Okta Open Source MCP Server is Okta's officially supported bridge between LLM agents and the Okta Admin Management APIs. It reached General Availability in February 2026, with human-oversight controls landing in March and customisation tools, scope-based loading and Device Assurance Policy tools reaching GA in June 2026.

It turns administrative workflows into natural language — "create a new user and add them to the Engineering group", "show me all failed login attempts from the last 24 hours", "list all applications that haven't been used in the past month" — while keeping the guardrails an identity provider needs.

Two design decisions carry most of the safety weight:

Scope-based tool loading. Tools are enabled or disabled at server startup based on the OAuth 2.0 scopes in OKTA_SCOPES. Tools whose scope has not been granted are removed before the first request, so the model never sees them. That enforces least privilege and cuts token consumption at the same time.

Elicitation on destructive actions. Deletes and deactivations prompt the operator for confirmation through the MCP Elicitation API, with an automatic fallback for clients that do not yet implement it.

Authentication supports the Device Authorization Grant for interactive use and Private Key JWT for browserless, server-to-server operation — the latter being the one you want in a container, since Docker cannot open a browser on the host.

Built on Okta's Python SDK v3.4.1; needs Python 3.13+ with the uv package manager, or Docker. Tool coverage spans users, groups, applications, policies, device assurance policies, brands, themes, custom pages, email templates, custom domains and email domains. Apache-2.0.

Best for identity and platform teams who want to automate Okta administration conversationally. Treat the scope configuration as the security boundary: whatever you grant in OKTA_SCOPES is what an agent can do to your directory.

Related MCP Servers

MCP: Mux MCP Server

by Mux

New

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

Developer Tools

MCP: ripwire

by Red Hat

New

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

Developer Tools

MCP: Graft

by Trail

New

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

Developer Tools

MCP: Expo MCP Server

by Expo

New

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Developer Tools

Browse all MCP servers →