Okta MCP Server & Agent Skill
Last updated
ibl.ai publishes a free Okta agent skill: a SKILL.md that teaches an AI agent to read and write Okta data and expose it as an MCP tool. Download it, connect your own Okta credentials, and run the agent on ibl.ai Agentic OS, where you own all the code and the data.
Okta is an identity platform for single sign-on, MFA and lifecycle management. An org stores users and their profiles, groups, application assignments, sign-on and security policies, and a system log of events.
What is the Okta API, and what can an agent read from it?
JSON REST APIs to manage users, groups, applications, policies and the System Log, e.g. /api/v1/users for listing, creating, updating and deleting users.
- API: Okta Management API (REST)
- Access: Issued by your administrator
- Base URL: https://{yourOktaDomain}/api/v1/
- Authentication: OAuth 2.0 client credentials with private_key_jwt (service app); API token (SSWS)
An Okta admin creates an API token, or registers an API service app, assigns it admin roles and grants Okta API scopes such as okta.users.read.
Service apps get scoped access tokens from https://{yourOktaDomain}/oauth2/v1/token; tokens last one hour. SSWS tokens inherit the creating admin's privileges and expire after 30 days unused. Okta recommends OAuth.
What can an agent read from Okta?
- Users β GET /api/v1/users and /api/v1/users/{id}; scope okta.users.read.
- Groups and memberships β List groups and the users in each group.
- Applications β List app integrations and which users or groups are assigned.
- System Log β Query sign-in and admin events, e.g. failed logins.
- Policies β Read sign-on and security policies and their rules.
What can an agent write to Okta?
- Create or update users β POST /api/v1/users and POST/PUT /api/v1/users/{id}; scope okta.users.manage.
- Group membership β Add or remove users from groups, which changes app access. Confirm with the user first.
- Deactivate or delete users β DELETE /api/v1/users/{id} removes a user and their access. Confirm with the user first.
- App assignments β Assign or unassign users and groups to applications. Confirm with the user first.
Limits: Rate limits vary by org and endpoint and are listed in the Rate Limit Dashboard; responses carry X-Rate-Limit-Limit, -Remaining and -Reset headers. Unauthenticated /oauth2/v1/token calls are limited to 4 per second.
Holds workforce and customer identity data: names, emails, phone numbers, group memberships and sign-in history. Writes change who can access every connected system; treat them as security-sensitive.
How do I connect Okta to an AI agent over MCP?
Okta, Inc. publishes an official MCP server: Okta Open Source MCP Server.
Self-hosted, Apache 2.0, in Okta's GitHub org. Device authorization or private key JWT; tools for users, groups, apps, policies, system logs load by granted scopes.
You can register that server on ibl.ai as it is, or use the SKILL.md below when you want the agent to call the Okta Management API directly.
On ibl.ai an MCP connection is three records, and a working integration always needs all three:
- Register the server β
POST β¦/mcp-servers/with its URL, a transport (sse,websocketorstreamable_http) and anauth_typeofnone,tokenoroauth2. - Create a connection that holds the credential, scoped to the whole organization (
platform), to a single agent, or to each user (user). - Enable it on the agent β
mcp-toolintool_slugsand the server id inmcp_servers. Both lists are replaced, not merged, so read the settings first.
For an API key or a service credential, one token connection at platform scope serves the whole organization; scope a connection to a single agent when that agent needs narrower access than the rest.
The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.
What does the Okta agent skill do?
The Okta skill is one SKILL.md file named iblai-connect-okta. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.
Save it as .claude/skills/iblai-connect-okta/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:
$ npx skills add iblai/vibe --allThis connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.
It was checked against Okta, Inc.'s documentation on October 20, 2026. Test it against your own Okta setup before you rely on it.
What can I ask an Okta agent to do?
- βShow failed sign-in attempts for jsmith@example.com in the last 24 hoursβ
- βWhich users are in the Finance group but not assigned to NetSuite?β
- βCreate a user for Ana Ruiz (ana.ruiz@example.com) and add her to Engineeringβ
- βList applications with no assigned usersβ
How do I run an Okta agent on ibl.ai?
Agentic OS is where the agent runs on ibl.ai: it holds the Okta MCP connection, the model the agent uses, its instructions and its conversation history.
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing β so you can deploy anywhere, from your own cloud to a fully air-gapped network.
- AI agents for Enterprise β what ibl.ai deploys in this sector
Which ibl.ai agents work with Okta data?
- IT Support β Enterprise
Which ibl.ai platform skills does an Okta agent use?
- /iblai-api-agent-mcp β MCP connectors for ibl.ai agents, end to end
- /iblai-vibe-agent-mcp β Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,β¦
- /iblai-api-agent-tool β Enable or disable an ibl.ai agent's tools via the platform API
What else should I know before connecting Okta to an AI agent?
Is there an official Okta MCP server?
Yes. Okta, Inc. publishes Okta Open Source MCP Server.
You can register it on ibl.ai as an MCP server, or use the SKILL.md when you want the agent to call the Okta Management API directly.
Who can get Okta API credentials?
An Okta admin creates an API token, or registers an API service app, assigns it admin roles and grants Okta API scopes such as okta.users.read.
Does Okta data leave my infrastructure when an ibl.ai agent uses it?
On ibl.ai, you own all the code and the data. Self-hosted in your cloud or data center, the agent, its MCP connections and its conversation logs stay inside your perimeter.
Because the platform is model-agnostic, you can point the agent at a model you host, so Okta records need not reach a third-party model provider.
Is the Okta agent skill free to use?
Yes. The SKILL.md is a free download with no sign-up. It assumes you already have Okta credentials, and your agreement with Okta, Inc. still governs how you use its API.
Which other data sources can an AI agent connect to alongside Okta?
Which other Enterprise systems have a connector?
- Canvas LMS β Learning management system
- Confluence β Team wiki and knowledge base
- Databricks β Data and AI platform (lakehouse)
- Docusign eSignature β Electronic signature platform
- Esri ArcGIS β Geographic information system (GIS)
- GitHub β Source code hosting and collaboration
- Google Workspace β Productivity and collaboration suite
- HubSpot β Customer relationship management (CRM)
- Jira β Work and issue tracking
- Microsoft 365 & SharePoint β Productivity and collaboration suite
- Oracle NetSuite β Cloud ERP and accounting
- PayPal β Online payments platform
- Salesforce β Customer relationship management (CRM)
- SAP S/4HANA β Enterprise resource planning (ERP)
- ServiceNow β IT service management and workflow platform
- Slack β Team messaging platform
- Snowflake β Cloud data warehouse
- Stripe β Online payments and billing platform
- Workday HCM β Human capital management (HCM)
- Zendesk Support β Customer service help desk
Every connector, grouped by sector, is on the connectors hub.