Okta MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OKTA_KEY_ID | No | Key ID for Private Key JWT authentication (required for browserless auth) | |
| OKTA_SCOPES | Yes | Space-separated list of OAuth scopes (e.g., 'okta.users.read okta.groups.read') | |
| OKTA_ORG_URL | Yes | Okta organization URL (e.g., https://dev-123456.okta.com) | |
| OKTA_LOG_FILE | No | Path to log file | |
| OKTA_CLIENT_ID | Yes | Okta client ID | |
| OKTA_LOG_LEVEL | No | Log level (e.g., DEBUG) | |
| OKTA_PRIVATE_KEY | No | Private key for Private Key JWT authentication (required for browserless auth) |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CerberusTrainer/Okta-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server