---
title: "Okta MCP server for AI agents - actionlake"
description: "Give Claude 646 Okta actions through one MCP server: directory, administration, applications. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/okta
updated: 2026-10-11
---

Connectors · Identity & security

# Okta MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Okta and the rest of your systems. It gives your agent 646 Okta actions (257 reads, 269 writes and 120 that wait for a confirmation) and holds the Okta credential itself, so the agent never does. It paces Okta's limits and records every call.

[Connect Okta free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "okta.users.list",
  intent: "check which Okta account is connected"
}
# List all users · read · 1 upstream call
```

- 646 actions in one signed file
- 257 read look, never change
- 269 write create and update
- 120 wait for a yes destructive, confirmed first

Set up

## Connect Okta in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Okta.
   API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `api_token` Okta API token
   - `org_host` Where your Okta lives: your org host
   ```
   account { op: "connections.requirements", service: "okta" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "okta.users.list" }
   # list all users · read · 1 upstream call
   check { action: "okta.users.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Okta at a glance

**Sign-in**

API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`api_token`

**Setup fields**

`org_host`

**Limits we pace to**

600 calls a minute, per connection

**API covered**

Okta API 1, at your Okta instance's API base URL, which you enter when connecting (path /api/v1)

**Built from**

Okta's documentation, read 15 September 2026[OpenAPI spec (GitHub)](https://raw.githubusercontent.com/okta/okta-sdk-java/master/src/swagger/api.yaml)

**Service file**

Version 2.0.0, signed (Ed25519)

**Cached reads**

227 of 257 reads, for up to an hour; a write clears what it affects

**Ready-made plans**

10 in the store

**Shared entities**

5, so ask can line Okta up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Okta.

646 actions in 12 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **257** read look, never change
- **269** write create and update
- **120** destructive wait for a confirmation

1. ### Directory
   299
   109 read · 127 write · 63 destructive
   List all users · List all groups · Create a user · Add a group
2. ### Administration
   79
   34 read · 35 write · 10 destructive
   List all custom roles · Create a custom role · Retrieve a role · Replace a custom role
3. ### Applications
   71
   29 read · 30 write · 12 destructive
   List all applications · Create an application · Preview the application SAML metadata · Retrieve an application
4. ### Branding
   49
   26 read · 13 write · 10 destructive
   List all domains associated with a brand · List all email templates · List all email customizations · Create an email customization
5. ### Oauth
   48
   18 read · 20 write · 10 destructive
   List all client resources for an authorization server · List all custom token scopes · List all associated authorization servers · List all policies
6. ### Federation
   26
   12 read · 10 write · 4 destructive
   List all users for IdP · Retrieve a user for IdP · List all tokens from OIDC IdP · List all IdPs
7. ### Schema
   23
   11 read · 9 write · 3 destructive
   Update the app user profile schema for an app · List all linked object definitions · Create a linked object definition · List all user types
8. ### Policy
   21
   7 read · 11 write · 3 destructive
   List all apps mapped to a policy · List all policies · List all policy rules · Clone an existing policy

**4 more areas · 30 actions**

- Authentication **18**
- Devices **8**
- Sessions **3**
- Audit **1**

Top actions

## The Okta API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 252 of Okta's 271 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `okta.users.list` List all users | List all users. Paged by Link header; each page is one upstream call. | read | `identity.user.list` 474 connectors |
| `okta.groups.list` List all groups | List all groups. Paged by Link header; each page is one upstream call. | read | `identity.group.list` 262 connectors |
| `okta.users.create` Create a user | Create a user. | write | `identity.user.create` 262 connectors |
| `okta.apps.list` List all applications | List all applications. Paged by Link header; each page is one upstream call. | read | `identity.application.list` 37 connectors |
| `okta.groups.add` Add a group | Add a group. | write | `identity.group.create` 205 connectors |
| `okta.custom_roles.list` List all custom roles | List all custom roles. Paged by Link header; each page is one upstream call. | read | `identity.role.list` 184 connectors |
| `okta.users.delete` Delete a user | Delete a user. Permanent — Okta does not soft-delete. | destructive | `identity.user.delete` 253 connectors |
| `okta.user_clients.list` List all clients | List all clients. Paged by Link header; each page is one upstream call. | read | `identity.application.list` 37 connectors |
| `okta.custom_roles.create` Create a custom role | Create a custom role. | write | `identity.role.create` 105 connectors |
| `okta.user_groups.list` List all groups | List all groups. Paged by Link header; each page is one upstream call. | read | `identity.group_member.list` 103 connectors |
| `okta.group_members.list` List all member users | List all member users. Paged by Link header; each page is one upstream call. | read | `identity.group_member.list` 103 connectors |
| `okta.group_roles.list_targets_role` List all group role group targets | List all group role group targets. Paged by Link header; each page is one upstream call. | read | `identity.role_assignment.list` 41 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Okta actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Okta devices have not checked in for a week?
   calls `okta.devices.list`
2. Plan destructive
   Offboard a user by cutting sessions, grants and factors in Okta. Ask me before anything is sent or changed.
   calls `okta.user_roles.list_assigned_roles` `okta.user_groups.list` `okta.user_clients.list_grants` `okta.user_sessions.revoke` `okta.user_clients.revoke_grants` +2 more
3. Plan read
   Investigate suspicious sign-in activity for a user in Okta.
   calls `okta.system_log.list_events` `okta.user_classification.get` `okta.user_factors.list_supported_factors` `okta.user_groups.list` `okta.user_app_links.list` +1 more
4. Write write
   Create a user in Okta. Show me exactly what you will send before you save it.
   calls `okta.users.create`

The plan store

## Ready-made plans for Okta.

10 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

1. ### Review which applications each group grants
   Use it when Preparing an access review or answering what applications a set of Okta groups grants access to.
   **Effect**
   read
   **Steps**
   3 · loops
   **Needs**
   group query and group rule id
   **Install**
   `okta-review-group-app-assignments`
2. ### Audit who holds admin roles across the org
   Use it when Someone asks for a privileged access review or wants to know who can administer Okta and with what permissions.
   **Effect**
   read
   **Steps**
   4 · loops
   **Needs**
   resource set
   **Install**
   `okta-audit-admin-role-assignments`
3. ### Investigate suspicious sign-in activity for a user
   Use it when A user's sign-ins look suspicious and an analyst needs the surrounding context before deciding whether to lock the account.
   **Effect**
   read
   **Steps**
   6
   **Needs**
   log filter, since and user id
   **Install**
   `okta-investigate-suspicious-signins`
4. ### Publish a themed sign-in page for a brand
   Use it when A brand's sign-in page or theme colours need updating and the change must be reviewed before it goes live to end users.
   A person decides Publish a new themed sign-in page on brand _brand id_ using widget version _widget version_ and primary colour _primary color hex_.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   brand id, page content, primary color hex, secondary color hex, theme id and widget version
   **Install**
   `okta-publish-brand-sign-in-page`
5. ### Roll out an agent pool update and wait for it to finish
   Use it when An Okta agent pool needs its auto-update scheduled, resumed and watched through to completion.
   A person decides Schedule and resume an agent update on pool _pool id_, which will briefly interrupt directory sync.
   **Effect**
   write
   **Steps**
   7
   **Needs**
   pool id, schedule and update id
   **Install**
   `okta-roll-out-agent-pool-update`
6. ### Decommission an external identity provider
   Use it when An external IdP federation is being retired or replaced and must be turned off cleanly.
   A person decides Deactivate identity provider _idp id_, which still has _number of items_ linked application users.
   **Effect**
   destructive
   **Steps**
   6
   **Needs**
   idp csr id and idp id
   **Install**
   `okta-decommission-identity-provider`
7. ### Quarantine a user flagged as high risk
   Use it when Threat detection or an analyst has flagged an account as compromised and it must be contained without deleting it.
   A person decides Set risk level _risk level_ on user _user id_ and revoke all their sessions and MFA factors.
   **Effect**
   destructive
   **Steps**
   6
   **Needs**
   risk level and user id
   **Install**
   `okta-quarantine-risky-user`
8. ### Retire a stale push provider and register its replacement origin
   Use it when A mobile push provider is being replaced and its trusted origin configuration needs swapping over at the same time.
   A person decides Delete push provider _push provider id_ and register _new origin_ as a trusted origin in its place.
   **Effect**
   destructive
   **Steps**
   6
   **Needs**
   new origin, new origin name, push provider id and trusted origin id
   **Install**
   `okta-retire-trusted-origin-and-push-provider`
9. ### Rotate the signing keys on an authorization server
   Use it when An authorization server's signing keys are due for rotation or are suspected of being compromised.
   A person decides Rotate signing keys on authorization server _name_, affecting _number of items_ client applications.
   **Effect**
   destructive
   **Steps**
   6
   **Needs**
   auth server id
   **Install**
   `okta-rotate-authz-server-keys`
10. ### Offboard a user by cutting sessions, grants and factors
    Use it when An employee has left or been suspended and their live Okta access must be cut immediately.
    A person decides Revoke all sessions, OAuth grants and MFA factors for user _user id_, who holds _number of items_ admin roles and _number of items_ group memberships.
    **Effect**
    destructive
    **Steps**
    8
    **Needs**
    client id and user id
    **Install**
    `okta-offboard-user-sessions-and-grants`

install a plan

```
account { op: "plans.install", slug: "okta-review-group-app-assignments" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Okta

## Destructive actions wait for a yes.

120 Okta actions are destructive. The first 10:

- Delete a user `okta.users.delete`
- Delete a group `okta.groups.delete`
- Delete an identity source user `okta.identity_sources.delete_user`
- Delete an application `okta.apps.delete`
- Delete a custom role `okta.custom_roles.delete`
- Deactivate a user `okta.user_lifecycle.deactivate`
- Unassign a user from a group `okta.group_members.unassign`
- Suspend a user `okta.user_lifecycle.suspend`
- Unassign a user role `okta.user_roles.unassign`
- Unassign a group role `okta.group_roles.unassign`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do okta.users.delete confirm_policy: **human**

Delete a user?

**intent:** the user asked me to delete a user

run suspended · waiting for a named person · key _okta-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "okta-agent",
  allowed_actions: ["okta.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "okta.users.delete", approver: "lead@example.com" },
    { match: "okta.groups.delete", approver: "lead@example.com" },
    { match: "okta.identity_sources.delete_user", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Okta only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Okta costs on actionlake.

Every Okta action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Okta refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 646 Okta actions
- 27 actions page each page of a long list is one call
- 227 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Okta action.

646 actions by area: the id your agent calls, what it does, and its effect.

**Directory 299**

- `okta.groups.add` Add a group write
- `okta.groups.list` List all groups read
- `okta.user_groups.list` List all groups read
- `okta.users.create` Create a user write
- `okta.users.list` List all users read
- `okta.agent_pools.activate_update` Activate an agent pool update write
- and 293 more in this area

**Administration 79**

- `okta.custom_roles.create` Create a custom role write
- `okta.custom_roles.get` Retrieve a role read
- `okta.custom_roles.list` List all custom roles read
- `okta.custom_roles.replace` Replace a custom role write
- `okta.custom_roles.create_permission` Create a custom role permission write
- `okta.custom_roles.delete` Delete a custom role destructive
- and 73 more in this area

**Applications 71**

- `okta.app_sso.preview_sam_lmetadata` Preview the application SAML metadata read
- `okta.apps.create` Create an application write
- `okta.apps.get` Retrieve an application read
- `okta.apps.list` List all applications read
- `okta.app_connections.activate_default_provisioning_connection` Activate the default provisioning connection write
- `okta.app_connections.deactivate_default_provisioning_connection` Deactivate the default provisioning connection write
- and 65 more in this area

**Branding 49**

- `okta.brand_domains.list` List all domains associated with a brand read
- `okta.email_templates.create_customization` Create an email customization write
- `okta.email_templates.list` List all email templates read
- `okta.email_templates.list_customizations` List all email customizations read
- `okta.brand_well_known.get_all_well_known_ur_is` Retrieve all the well-known URIs read
- `okta.brand_well_known.get_root_brand_well_known_uri` Retrieve the well-known URI of a specific brand read
- and 43 more in this area

**Oauth 48**

- `okta.authz_associated.list_servers_by_trusted_type` List all associated authorization servers read
- `okta.authz_clients.list` List all client resources for an authorization server read
- `okta.authz_policies.list_server_policies` List all policies read
- `okta.authz_scopes.list` List all custom token scopes read
- `okta.authz_associated.create_servers` Create an associated authorization server write
- `okta.authz_associated.delete_server` Delete an associated authorization server destructive
- and 42 more in this area

**Federation 26**

- `okta.idp_users.get_identity_provider_application_user` Retrieve a user for IdP read
- `okta.idp_users.list_identity_provider_application_users` List all users for IdP read
- `okta.idp_users.list_social_auth_tokens` List all tokens from OIDC IdP read
- `okta.idps.list` List all IdPs read
- `okta.idp_csrs.generate` Generate a certificate signing request write
- `okta.idp_csrs.get` Retrieve a certificate signing request read
- and 20 more in this area

**Schema 23**

- `okta.app_schemas.update_application_user_profile` Update the app user profile schema for an app write
- `okta.user_schemas.create_linked_object_definition` Create a linked object definition write
- `okta.user_schemas.list_linked_object_definitions` List all linked object definitions read
- `okta.user_types.list` List all user types read
- `okta.app_schemas.get_application_user_schema` Retrieve the default app user schema for an app read
- `okta.group_schemas.get` Retrieve the default group schema read
- and 17 more in this area

**Policy 21**

- `okta.policies.clone` Clone an existing policy write
- `okta.policies.list` List all policies read
- `okta.policies.list_apps` List all apps mapped to a policy read
- `okta.policy_rules.list` List all policy rules read
- `okta.policies.activate` Activate a policy write
- `okta.policies.create` Create a policy write
- and 15 more in this area

**Authentication 18**

- `okta.authenticator_aaguids.create_custom_aaguid` Create a custom AAGUID write
- `okta.authenticator_aaguids.list_all_custom_aagui_ds` List all custom AAGUIDs read
- `okta.authenticator_methods.list` List all methods of an authenticator read
- `okta.authenticators.list` List all authenticators read
- `okta.authenticator_aaguids.delete_custom_aaguid` Delete a custom AAGUID destructive
- `okta.authenticator_aaguids.get_custom_aaguid` Retrieve a custom AAGUID read
- and 12 more in this area

**Devices 8**

- `okta.devices.activate` Activate a device write
- `okta.devices.delete` Delete a device destructive
- `okta.devices.get` Retrieve a device read
- `okta.devices.list` List all devices read
- `okta.devices.deactivate` Deactivate a device destructive
- `okta.devices.list_users` List all users for a device read
- and 2 more in this area

**Sessions 3**

- `okta.sessions.get` Retrieve a session read
- `okta.sessions.refresh` Refresh a session write
- `okta.sessions.revoke` Revoke a session destructive

**Audit 1**

- `okta.system_log.list_events` List all System Log events read

This index shows a sample of each area. All 646 actions, with their inputs and prices, are in the [catalogue](https://actionlake.com/console/catalogue), which a free sandbox key can search.

Questions

## The Okta MCP server, answered.

**Is there an Okta MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 646 Okta actions across directory, administration, applications and branding, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Okta.

**What do I need to connect Okta?**

Okta API token. Plus your org host. The free call account { op: "connections.requirements", service: "okta" } lists exactly what to paste.

**Can an AI agent delete or change things in Okta?**

Only if its key allows it, and only with an explicit confirmation. 120 Okta actions are destructive, including delete a user, delete a group and delete an identity source user. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Okta API limit?**

actionlake paces every call to the limits in the Okta service file: 600 calls a minute per connection. Repeated reads are answered from cache (227 Okta actions can be), which never reaches Okta.

**What does an Okta action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (27 Okta actions page). Cache hits, searches, dry runs and calls Okta refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Okta API does it cover?**

The Okta API 1 at your Okta instance's API base URL, which you enter when connecting (path /api/v1). It is built from Okta's documentation as read on 15 September 2026. 646 actions in 12 areas, each one in the signed service file (version 2.0.0).

**Does actionlake keep my Okta data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Okta credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Okta

Shares the most action names with

- [JumpCloud 94](https://actionlake.com/connectors/jumpcloud)
- [Microsoft 365 Users 91](https://actionlake.com/connectors/microsoft-365-users)
- [PingOne Platform API 56](https://actionlake.com/connectors/pingone-platform-api)
- [Google Workspace Directory 51](https://actionlake.com/connectors/google-workspace-directory)
- [Clerk 43](https://actionlake.com/connectors/clerk)
- [FusionAuth 37](https://actionlake.com/connectors/fusionauth)

Joins with, on shared entities

- [Commvault Cloud 4](https://actionlake.com/connectors/commvault-cloud)
- [authentik 4](https://actionlake.com/connectors/authentik)
- [Sophos Central 4](https://actionlake.com/connectors/sophos-central)
- [Zabbix 4](https://actionlake.com/connectors/zabbix)
- [Material Security 4](https://actionlake.com/connectors/material-security)
- [HaloPSA 3](https://actionlake.com/connectors/halopsa)

Browse

- [All Identity & security connectors](https://actionlake.com/connectors/category/identity-and-security)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Okta; the name is the vendor's own. Counts are from the Okta service file, version 2.0.0.

## Give your agent Okta today.

[Connect Okta free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/okta
More: https://actionlake.com/llms.txt