OktaSAFE
Okta MCP Server
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://mseep.ai/app/kapilduraphe-okta-mcp-server)
This MCP server enables Claude to interact with Okta's user management system, providing comprehensive user and group management capabilities along with onboarding automation.
Prerequisites
- Node.js (v16 or higher)
- Claude Desktop App
- Okta Developer Account
- Admin API Token from Okta
Setup Instructions
1. Create an Okta Developer Account
- Go to the Okta Developer Console
- Create a new account or sign in to an existing one
- Note your Okta domain (e.g.,
dev-123456.okta.com)
2. Create an API Token
- In the Okta Developer Console, go to Security > API > Tokens
- Click "Create Token"
- Give your token a meaningful name (e.g., "MCP Server Token")
- Copy the token value (you won't be able to see it again)
3. Initial Project Setup
Install dependencies:
npm install
4. Configure Claude Desktop
Open your Claude Desktop configuration file:
For MacOS:
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
For Windows:
code %AppData%\Claude\claude_desktop_config.json
Add or update the configuration:
{
"mcpServers": {
"okta": {
"command": "node",
"args": [
"PATH_TO_PROJECT_DIRECTORY/dist/index.js"
],
"env": {
"OKTA_ORG_URL": "https://your-domain.okta.com",
"OKTA_API_TOKEN": "your-api-token"
}
}
}
}Save the file and restart Claude Desktop.
Available Tools
The server provides the following tools:
User Management
get_user
Ret
8d6d4b4e6f3dOBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add okta-mcp-server --env OKTA_API_TOKEN=${OKTA_API_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"okta-mcp-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"OKTA_API_TOKEN": "${OKTA_API_TOKEN}"
}
}
}
}Exposed tools (21)
14 read · 4 write · 3 destructive. Blast radius: 3 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
activate_user | read | Activate a user in Okta |
assign_user_to_group | read | Assign a user to a group in Okta |
assign_users_to_groups | read | Assign multiple users to groups based on attributes |
bulk_user_import | write | Import multiple users from a CSV string |
create_group | write | Create a new group in Okta |
create_user | write | Create a new user in Okta |
deactivate_user | read | Deactivate a user in Okta |
delete_group | destructive | Delete a group from Okta |
delete_user | destructive | Delete a user from Okta (must be deactivated first) |
find_users_by_attribute | read | Search users by any profile attribute (manager, department, title, firstName, etc.) |
get_group | read | Get detailed information about a specific group |
get_user | read | Retrieve detailed user information from Okta by user ID |
get_user_last_location | read | Retrieve the last known location and login information for a user from Okta system logs |
list_group_users | read | List all users in a specific group |
list_groups | read | List user groups from Okta with optional filtering and pagination |
list_users | read | List users from Okta with optional filtering and pagination |
provision_applications | read | Provision application access for multiple users |
remove_user_from_group | destructive | Remove a user from a group in Okta |
run_onboarding_workflow | write | Run a complete onboarding workflow for multiple users from CSV data |
suspend_user | read | Suspend a user in Okta |
unsuspend_user | read | Unsuspend a user in Okta |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
delete_group, delete_user, remove_user_from_group
@okta/okta-sdk-nodejs, @modelcontextprotocol/sdk, dotenv, zod, papaparse, @types/node, prettier, ts-node
Gates applied: no_behavioural_pass.
8d6d4b4e6f3dfull audit observations/trust-audit/mcp-server/kapilduraphe__okta.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 8d6d4b4e6f3d | SAFE | B | 89 | first audit |
Questions
What is the Okta MCP server?
Okta MCP Server
What tools does Okta expose?
21 in total: 14 read-only, 4 that write, and 3 that can delete or overwrite (delete_group, delete_user, remove_user_from_group). Every one is listed on this page with its risk.
Is Okta safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 3 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Okta need?
It reads OKTA_API_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Okta run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as okta-mcp-server at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (8d6d4b4e6f3d), read on 2026-10-10. The repository is watched and re-audited when it changes.