Okta MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OKTA_ORG_URL | Yes | Your Okta organization URL (e.g., https://dev-123456.okta.com) | |
| OKTA_API_TOKEN | Yes | Your Okta API token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userB | Retrieve detailed user information from Okta by user ID |
| list_usersB | List users from Okta with optional filtering and pagination |
| create_userC | Create a new user in Okta |
| activate_userC | Activate a user in Okta |
| suspend_userC | Suspend a user in Okta |
| unsuspend_userC | Unsuspend a user in Okta |
| deactivate_userC | Deactivate a user in Okta |
| delete_userA | Delete a user from Okta (must be deactivated first) |
| get_user_last_locationC | Retrieve the last known location and login information for a user from Okta system logs |
| list_groupsC | List user groups from Okta with optional filtering and pagination |
| create_groupC | Create a new group in Okta |
| get_groupC | Get detailed information about a specific group |
| delete_groupC | Delete a group from Okta |
| assign_user_to_groupC | Assign a user to a group in Okta |
| remove_user_from_groupC | Remove a user from a group in Okta |
| list_group_usersC | List all users in a specific group |
| bulk_user_importC | Import multiple users from a CSV string |
| assign_users_to_groupsC | Assign multiple users to groups based on attributes |
| provision_applicationsC | Provision application access for multiple users |
| run_onboarding_workflowC | Run a complete onboarding workflow for multiple users from CSV data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool has a clearly distinct purpose targeting specific resources (users, groups, applications) and actions (create, get, list, activate, assign, etc.). There is no significant overlap; for example, assign_user_to_group and assign_users_to_groups differ in scope but are clearly distinguished by their descriptions.
Tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly. Verbs like create, get, list, assign, delete, etc., are applied predictably to nouns like user, group, or specific operations, making the set highly readable and systematic.
With 20 tools, the count is slightly high but reasonable for an Okta server covering user and group management, onboarding, and application provisioning. It includes core CRUD operations and specialized workflows, though it might be borderline heavy for some agents.
The tool surface provides comprehensive coverage for Okta's domain, including full CRUD/lifecycle operations for users and groups (e.g., create, get, list, activate/deactivate, suspend/unsuspend, delete), bulk operations, assignment workflows, and application provisioning, with no obvious gaps for core administrative tasks.