Skip to content

SSO

Okta MCP connector

The Okta connector brings your users, groups, applications, admin roles, and system logs into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so each person can look up and manage accounts within their own Okta access, with every action logged.

  • OAuth or API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which Okta users were deactivated in the last week?

Working in Okta with Elaichi

  • Get single Okta user by ID
  • Okta users list subscriptions
  • Get single Okta group by ID
Ask anything…
Governance / Audit log Last 24 hours
Okta Get single Okta group by ID Emily Carter · Claude · 9:41 AM Done
Okta Okta users list subscriptions Emily Carter · Claude · 9:41 AM Done
Okta Get single Okta user by ID Emily Carter · Claude · 9:41 AM Done
Okta Create a Okta user Megan Brooks · ChatGPT · 9:38 AM Done
Okta Update a Okta user by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Okta to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Okta MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Okta MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Okta MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Okta MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Okta MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Okta to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Okta through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Okta is logged.

  • IT

    Set up a new hire on day one

    Create the Okta user, add them to the right groups, and confirm which applications they can now reach, all from one request.

  • IT

    Deactivate a leaver before their laptop is returned

    Suspend or deactivate the Okta account the moment HR confirms a departure, and check that every group membership is gone.

  • Helpdesk

    Answer why someone cannot sign in

    Pull up the user, see their status and groups, and read the recent Okta system log entries for that person to find the failed sign-in or locked account.

  • Security

    Review who holds admin roles

    List every Okta role and who is assigned to it, then flag accounts that hold more than the job needs.

  • Security

    Investigate a suspicious sign-in

    Search the Okta system log for a user, an application, or a time window and get a plain summary of what happened and from where.

  • HR

    Keep group membership matched to the org chart

    After a team move, update the user's details and swap their Okta group memberships so application access follows the new role.

Try asking

  • “Which Okta users were deactivated in the last week?”
  • “List members of the Engineering Okta group.”
  • “Show Okta users suspended but still in groups.”

See all 318 Okta tools →

What connecting Okta gets you

6 screens from Elaichi, each doing one job for your Okta account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which Okta users were deactivated in the last week?

List members of the Engineering Okta group.

Show Okta users suspended but still in groups.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Okta users, get real answers.

Plain language questions run against live Okta users, groups and memberships.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One Okta endpoint for every MCP client.

Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK, no shared API key.

ElaichiTools
Tool Action Description
Get single Okta user by ID Get Get a single Okta user by id. Returns the full user object including profile, status, and credential details. Required: id.
Create a Okta user Create Create a new user in Okta. Returns the created user object including its id, status, and profile.
Update a Okta user by ID Update Replace an existing Okta user's profile and credentials in full via PUT. Returns the updated user object. Required: id.
Delete a Okta user by ID Delete Delete an Okta user by id. Returns an empty response on success. Required: id.
Okta users deactivate Deactivate Deactivate an Okta user, transitioning them to the DEPROVISIONED lifecycle state. Returns an empty response on success. Required: user_id.

Tool catalog

318 Okta tools ready to call.

Users, groups, members and subscriptions covered, with no custom code to write.

ElaichiToolboxes
Name Source template Tools Created

IT Operations toolbox

Okta · users and deactivations

Okta starter 18 Mar 4, 2026

Security toolbox

Okta · suspensions and group membership

— 9 Mar 2, 2026

People Ops toolbox

Okta · joiners and profile updates

— 24 Feb 27, 2026

Engineering toolbox

Okta · group members and subscriptions

Okta starter 6 Feb 19, 2026

Support toolbox

Okta · user lookups and resets

— 31 Jan 30, 2026

Compliance toolbox

Okta · access reviews and audit

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Okta toolbox.

Curate one toolbox per team so each sees only the Okta tools it needs.

ElaichiConnections
Connection Scope Status Access
OK

Okta (IT Core)

Connected by Emily Carter

Personal • Active 1 team · 6 members
OK

Okta (Security EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
OK

Okta (People Ops)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
OK

Okta (Support Desk)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
OK

Okta (Engineering)

Connected by Ryan Hayes

Personal • Active Not shared
OK

Okta (Contractors)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share Okta access, never the credential.

Teammates run user and group calls through a connection they cannot read.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Okta Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Okta Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Okta Users List Toolbox

Audit log

Every Okta call is on the record.

When, who, what happened, type and resource for each user and group change.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Okta digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch users

    Okta

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Okta

    Queued

Automations

A schedule fires, Okta work gets done.

Fetch users, group them, draft a digest, get approval, post back to Okta.

Okta health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Groups

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

IT Core 34%

Security EMEA 27%

People Ops 21%

Support Desk 18%

Collections and dashboards

Okta numbers computed, not requested.

Four metrics, 14 days of users created and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Okta

All three can connect Okta to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Okta, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Okta tools Allow or restrict single Okta tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Okta call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Okta tools for your AI agents

318 tools are ready to call through Elaichi's MCP endpoint the moment you connect Okta, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Okta to Claude?

First connect Okta in Elaichi, then paste the endpoint https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Okta is one of the few applications where an Okta administrator registers an OAuth application inside Okta and brings the client ID and secret to Elaichi once, or connects with an Okta API token instead. After that one-time step, everyone else simply signs in to Okta as themselves when they connect.

Does Okta work with ChatGPT and Cursor as well as Claude?

Yes. Once Okta is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Okta once and every client sees it.

What can an AI agent actually do with my Okta data?

With Okta connected, you can ask an agent to look up a user, create one, update their details, suspend or deactivate them, or change their group memberships. It can list your Okta applications, show who holds which admin role, assign a role, and read the system log to explain a failed sign-in. Because Okta exposes a large number of actions, short concrete asks such as "deactivate Jane Smith" work better than long paragraphs.

Does connecting Okta give the AI admin rights over my whole organization?

No. Every request to Okta runs inside the access of the person who signed in, so a helpdesk agent who cannot deactivate users in Okta cannot do it through an AI either. Elaichi can narrow that access further with per-action restrictions, and it can never widen it beyond what Okta already allows that person.

Can my team share one Okta connection?

Yes. One Okta administrator connects the account in Elaichi and shares it with a team, and nobody else ever handles the client secret or API token. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Okta change.

Can I stop an agent from deleting or changing things in Okta?

Yes. In Elaichi you can restrict individual Okta actions, such as deleting users, deleting applications, or assigning admin roles, while leaving lookups and group changes available. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

What happens to an Okta connection when someone leaves?

Offboarding a person in Elaichi ends their access to Okta through every AI client at once. If they had shared an Okta connection with a team, it keeps working for everyone else. Disconnecting Okta once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.

Does the Okta MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Okta is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Okta?

Yes. Both let Claude, ChatGPT or Cursor use Okta. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Okta call.

How is Elaichi different from Composio for Okta?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Okta: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Okta in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot