Okta MCP Server

🚀 Okta MCP Server

The Okta MCP Server integrates with LLMs and AI agents, enabling users to perform various Okta management operations using natural language. It standardizes how large language models communicate with external tools, resources, or remote services, enhancing automation and management capabilities.

⚠️ Important Note

Beta Software Notice: This software is currently in beta and is provided AS IS without any warranties.

• Features, APIs, and functionality may change at any time without notice
• Not recommended for production use or critical workloads
• Support during the beta period is limited
• Issues and feedback can be reported through the GitHub issue tracker

By using this beta software, you acknowledge and accept these conditions.

🚀 Quick Start

Prerequisites

• Python 3.8+
• uv package manager
• Claude Desktop or any other MCP Client
• Okta account with appropriate permissions

Install the Okta MCP Server

Install Okta MCP Server and configure it to work with your preferred MCP Client.

Claude Desktop with all tools

1. Clone and install the server:

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

2. Configure Claude Desktop by adding the following to your claude_desktop_config.json:

   {
     "mcpServers": {
       "okta-mcp-server": {
         "command": "uv",
         "args": [
           "run",
           "--directory",
           "/path/to/okta-mcp-server",
           "okta-mcp-server"
         ],
         "env": {
           "OKTA_ORG_URL": "<OKTA_ORG_URL>",
           "OKTA_CLIENT_ID": "<OKTA_CLIENT_ID>",
           "OKTA_SCOPES": "<OKTA_SCOPES>",
           "OKTA_PRIVATE_KEY": "<PRIVATE_KEY_IF_NEEDED>",
           "OKTA_KEY_ID": "<KEY_ID_IF_NEEDED>"
         }
       }
     }
   }
   

VS Code

Add the following to your VS Code settings.json:

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "description": "Okta Organization URL (e.g., https://dev-123456.okta.com)",
        "id": "OKTA_ORG_URL"
      },
      {
        "type": "promptString",
        "description": "Okta Client ID",
        "id": "OKTA_CLIENT_ID",
        "password": true
      },
      {
        "type": "promptString",
        "description": "Okta Scopes (separated by whitespace, e.g., 'okta.users.read okta.groups.manage')",
        "id": "OKTA_SCOPES"
      },
      {
        "type": "promptString",
        "description": "Okta Private Key. Required for 'browserless' auth.",
        "id": "OKTA_PRIVATE_KEY",
        "password": true
      },
      {
        "type": "promptString",
        "description": "Okta Key ID (KID) for the private key. Required for 'browserless' auth.",
        "id": "OKTA_KEY_ID",
        "password": true
      }
    ],
    "servers": {
      "okta-mcp-server": {
        "command": "uv",
        "args": [
          "run",
          "--directory",
          "/path/to/the/okta-mcp-server",
          "okta-mcp-server"
        ],
        "env": {
          "OKTA_ORG_URL": "${input:OKTA_ORG_URL}",
          "OKTA_CLIENT_ID": "${input:OKTA_CLIENT_ID}",
          "OKTA_SCOPES": "${input:OKTA_SCOPES}",
          "OKTA_PRIVATE_KEY": "${input:OKTA_PRIVATE_KEY}",
          "OKTA_KEY_ID": "${input:OKTA_KEY_ID}"
        }
      }
    }
  }
}

Other MCP Clients

To use Okta MCP Server with any other MCP Client, you can manually add this configuration to the client and restart for changes to take effect:

{
  "mcpServers": {
    "okta-mcp-server": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/path/to/okta-mcp-server",
        "okta-mcp-server"
      ],
      "env": {
        "OKTA_ORG_URL": "<OKTA_ORG_URL>",
        "OKTA_CLIENT_ID": "<OKTA_CLIENT_ID>",
        "OKTA_SCOPES": "<OKTA_SCOPES>",
        "OKTA_PRIVATE_KEY": "<PRIVATE_KEY_IF_NEEDED>",
        "OKTA_KEY_ID": "<KEY_ID_IF_NEEDED>"
      }
    }
  }
}

Authenticate with Okta

The server supports two authentication methods. Choose the one that best fits your use case.

Method 1: Device Authorization Grant (Interactive)

1. In your Okta org, create a new App Integration.
2. Select OIDC - OpenID Connect and Native Application.
3. Under Grant type, ensure Device Authorization is checked.
4. Go to the Okta API Scopes tab and Grant permissions for the APIs you need (e.g., okta.users.read, okta.groups.manage).
5. Save the application and copy the Client ID.
6. Documentation: Okta Device Authorization Grant Guide

Method 2: Private Key JWT (Browserless)

1. Create App: In your Okta org, create a new App Integration. Select API Services. Save the app and copy the Client ID.
2. Configure Client Authentication:
   • On the app's General tab, find the Client Credentials section and click Edit.
   • Disable Require Demonstrating Proof of Possession (DPoP) header in token requests.
   • Select Public key / Private key for the authentication method.
3. Add a Public Key: You have two options for adding a key.
   • Option A: Generate Key in Okta (Recommended)
     1. In the Public keys section, click Add key.
     2. In the dialog, choose Generate new key.
     3. Okta will instantly generate a key pair. Download or save the private key (private.pem) and store it securely.
     4. Copy the Key ID (KID) displayed for the newly generated key.
   • Option B: Use Your Own Key
     1. Generate a key pair locally using the following openssl commands:

        # Generate a 2048-bit RSA private key
        openssl genpkey -algorithm RSA -out private.pem -pkeyopt rsa_keygen_bits:2048
        
        # Extract the public key from the private key
        openssl rsa -in private.pem -pubout -out public.pem
        

     2. Click Add key and paste the contents of your public key (public.pem) into the dialog.
     3. Copy the Key ID (KID) displayed for the key you added.
4. Grant API Scopes: Go to the Okta API Scopes tab and Grant permissions for the APIs you need.
5. Assign Admin Roles: To avoid 403 Forbidden errors, go to the Admin roles tab and assign the Super Administrator role to this application.

Verify your integration

Restart your MCP Client (Claude Desktop, VS Code, etc.) and ask it to help you manage your Okta tenant:

Show me the users in my Okta organization

✨ Features

• LLM-Driven Okta Management: Allows your LLM agents to perform administrative tasks within your Okta environment based on natural language instructions.
• Secure Authentication: Supports both Device Authorization Grant for interactive use and Private Key JWT for secure, automated server-to-server communication.
• Integration with Okta Admin Management APIs: Leverages the official Okta APIs to ensure secure and reliable interaction with your Okta org.
• Extensible Architecture: Designed to be easily extended with new functionalities and support for additional Okta API endpoints.
• Comprehensive Tool Support: Full CRUD operations for users, groups, applications, policies, and more.

💻 Usage Examples

Basic Usage

You could simply ask Claude Desktop to perform Okta management operations:

- 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

📚 Documentation

Supported Tools

The Okta MCP Server provides the following tools for LLMs to interact with your Okta tenant:

Users

Groups

Applications

Policies

Logs

🔧 Technical Details

Authentication

The Okta MCP Server uses the Okta Management API and requires authentication to access your Okta tenant.

Authentication Flow

The server uses OAuth 2.0 device authorization flow for secure authentication with Okta, or Private Key JWT for browserless authentication. Your credentials are managed securely and are never exposed in plain text.

Initial Setup

The MCP Server will automatically initiate the appropriate authentication flow based on your configuration:

• Device Authorization Grant: Interactive browser-based authentication
• Private Key JWT: Browserless authentication using client credentials

💡 Usage Tip

Device authorization flow is not supported for private cloud tenants. Private Cloud users should use Private Key JWT authentication with client credentials.

⚠️ Important Note

Using the MCP Server will consume Management API rate limits according to your subscription plan. Refer to the Rate Limit Policy for more information.

🩺 Troubleshooting

🐞 Debug Mode

Enable debug mode for more detailed logging:

export OKTA_LOG_LEVEL=DEBUG

💡 Usage Tip

Debug mode is particularly useful when troubleshooting connection or authentication issues.

🚨 Common Issues

1. Authentication Failures

   • Ensure you have the correct permissions in your Okta tenant
   • Verify your OKTA_ORG_URL, OKTA_CLIENT_ID, and OKTA_SCOPES are correct
   • Check that your application has the necessary API scopes granted

2. MCP Client Can't Connect to the Server

   • Restart your MCP client after installation
   • Verify the server path is correct in your configuration
   • Check that uv is installed and accessible in your PATH

3. API Errors or Permission Issues

   • Enable debug mode with export OKTA_LOG_LEVEL=DEBUG
   • Verify your Okta application has the required scopes
   • Ensure your application has appropriate admin roles assigned
   • Check the Okta System Log for detailed error information

4. "Claude's response was interrupted..." Error

   • This typically happens when Claude hits its context-length limit
   • Try to be more specific and keep queries concise
   • Break large requests into smaller, focused operations

💡 Usage Tip

Most connection issues can be resolved by restarting both the server and your MCP client.

👨‍💻 Development

Building from Source

# Clone the repository
git clone https://github.com/okta/okta-mcp-server.git
cd okta-mcp-server

# Install dependencies
uv sync

# Run the server directly
uv run okta-mcp-server

Development Scripts

# Run with debug logs enabled
OKTA_LOG_LEVEL=DEBUG uv run okta-mcp-server

# Run tests
uv run pytest

# Install in development mode
uv pip install -e .

💡 Usage Tip

This server requires Python 3.8 or higher and uv.

🔒 Security

The Okta MCP Server prioritizes security:

• Credentials are managed through secure authentication flows
• No sensitive information is stored in plain text
• Authentication uses OAuth 2.0 device authorization flow or Private Key JWT
• Supports fine-grained API scope permissions
• Easy credential management through environment variables

⚠️ Important Note

For security best practices, always review the permissions requested during the authentication process to ensure they align with your security requirements.

⚠️ Important Note

Always use the principle of least privilege when granting API scopes to your Okta application.

🧪 Security Scanning

We recommend regularly scanning this server, and any other MCP-compatible servers you deploy, with community tools built to surface protocol-level risks and misconfigurations.

These scanners help identify issues across key vulnerability classes including: server implementation bugs, tool definition and lifecycle risks, interaction and data flow weaknesses, and configuration or environment gaps.

If you discover a vulnerability, please follow our responsible disclosure process.

💬 Feedback and Contributing

We appreciate feedback and contributions to this project! Before you get started, please see:

• Okta's general contribution guidelines

Reporting Issues

To provide feedback or report a bug, please raise an issue on our issue tracker.

Vulnerability Reporting

Please do not report security vulnerabilities on the public GitHub issue tracker. Please follow the responsible disclosure process.

📄 License

This project is licensed under the Apache 2.0 license. See the LICENSE file for more info.

What is Okta?

Okta is the leading independent identity provider. To learn more checkout Why Okta?

Copyright © 2025-Present, Okta, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.