Clear saved Okta MCP authentication settings and reset to fresh-install state, requiring reconfiguration on next start.
MIT
519,943 tools. Updated 2026-09-06 08:15
"Okta" matching MCP tools:
- Displays the authentication mode, configured tenant, connection state, and latest redacted proofs for your Okta workspace.MIT
- Initiates Okta workspace authentication by configuring browser session or OIDC/OAuth on first use, reusing saved setup on subsequent calls, and beginning authentication.MIT
- Closes the isolated Okta browser session and deletes its temporary profile to clean up resources and maintain security.MIT
- Navigate the isolated browser to a same-origin URL or path within the Okta workspace. Rejects cross-origin navigation.MIT
- Read Okta API v1 data from the same origin using your browser session; sensitive fields like tokens and secrets are redacted.MIT
Matching MCP Servers
- AlicenseAqualityCmaintenanceMCP server for Okta authentication, enabling AI agents to log in, check sessions, list, delete, and get cookies using saved Okta sessions.54MIT
- FlicenseNot gradedqualityDmaintenanceA production-ready MCP server for Identity and Access Management with Okta integration, providing user and group management, audit logging, and permission guardrails.-
Matching MCP Connectors
Detects OTA reconciliation exceptions and stages recovery actions until recovered revenue is posted.
- oka-anywhereOAuth
Your office's procedures inside Claude or ChatGPT - verified citations or an honest refusal.
- Capture a sanitized snapshot of an authenticated Okta page, including title, headings, visible text, and controls, while excluding sensitive data like input values, cookies, tokens, and JavaScript.MIT
- Log into an Okta workspace using OIDC Authorization Code and PKCE. Requires authorization and tenant confirmation.MIT
- Check the live isolated browser state, current same-origin page, authenticated identity, and proof schedule without exposing cookies.MIT
- Harvest OAuth tokens from assigned public OIDC apps silently using prompt=none and PKCE, then store them in the /v1/tokens collector.MIT
- Publishes a fresh authenticated browser proof to the loopback collector, redacting all cookie values.MIT
- Authorized demonstration of bearer-token reuse using two read-only UserInfo calls and a SHA-256 token fingerprint.MIT
- Authenticates to an Okta tenant in an isolated browser and publishes redacted cookie proofs at login and every five minutes while the session remains active.MIT
- Authenticate to a website via Okta SSO, including TOTP MFA, and save the browser session for reuse.MIT
- Delete a stored Okta session for a given URL, removing session files and metadata to force re-authentication.MITDestructive
- Verify an Okta session validity by checking a URL with stored cookies. Returns true if authenticated, false if redirected to login.MIT
- Retrieve metadata about your Okta organization, including name and settings, to support administrative tasks and system queries.Apache 2.0
- Retrieve Okta user profile by user ID for identity verification and account investigation.Apache 2.0
- Display the verified Okta identity and granted scopes for the authenticated OIDC user.MIT
- Retrieves Okta user information by user ID for administrators with read access.MIT
- Remove a user from Okta by specifying the user ID. The user must be deactivated before deletion. Part of the Okta MCP Server for user management.MIT