MCP client configuration overview
Configure the Okta Managed MCP Server in your AI client by adding connection parameters to establish secure authentication and enable natural language interactions.
Early Access release
The Okta Managed MCP Server is hosted in the cloud, so you don't need to download packages or manage local server processes. Instead, you configure OIDC app integrations to authorize connections between your AI workspace tools and the Okta Managed MCP Server. Then you configure your MCP client with the server's connection details, such as the server URL. The Okta Managed MCP Server endpoint uses this format: https://{yourOktaDomain}/mcp. Some clients connect to the Okta Managed MCP Server automatically after this step, while others require you to start the connection manually. Verify the connection to your org, and then use natural language commands to perform admin tasks.
The Okta Managed MCP Server supports the 2025-11-25 MCP protocol version. MCP clients that don't support this protocol version can't connect to the server. This guide focuses on specific configuration for VS Code with GitHub Copilot, but you can apply the same configuration approach to other MCP clients that support the 2025-11-25 protocol version, such as Claude Desktop, Gemini, or Amazon Bedrock.