Okta app authentication for the Okta Managed MCP Server overview

Understand how to configure an Okta app integration with OAuth 2.0 authentication, obtain credentials, and grant the required API scopes to authorize your Okta Managed MCP Server to access your Okta org.

Early Access release

Overview

This guide explains how to create an Okta app integration and generate authentication credentials for the Okta Managed MCP Server to interact with your Okta org. You'll get the client ID and identify the OAuth 2.0 scopes required for your use cases, and understand how scope-based tool loading controls which tools are available to your MCP client. Choose the authentication method that fits your use case:

• OpenID Connect (OIDC) with Proof Key for Code Exchange (PKCE) for authentication: Used for interactive tasks and user-facing apps. Ideal for desktop clients like VS Code.
• Private key JWT: Recommended for autonomous agents and backend services that run without human intervention. Ideal for CI/CD pipelines and non-interactive environments.

If your org needs different scopes for different user types, see Configure apps for multiple user types instead.

Tasks

• You have an MCP client such as VS Code.
• You have HTTPS connectivity for secure communication between client and server.
• You have network access to Okta org endpoints.