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
When you create an Okta app integration, you can generate authentication credentials for the Okta Managed MCP Server to interact with your Okta org. You get the client ID and identify the OAuth 2.0 scopes that your use cases require. You also learn how scope-based tool loading controls which tools your MCP client can use. The Okta Managed MCP Server uses OpenID Connect (OIDC) with Proof Key for Code Exchange (PKCE) for authentication. This method is used for interactive tasks and user-facing apps, and is ideal for desktop clients like VS Code.
If you have the Okta for AI Agents license and want to secure AI agent tool calls with an Agent Gateway, see Set up the Okta Managed MCP Server from the OIN catalog instead.
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.