Skip to main content
Glama
oreneHack

Okta Workspace MCP

by oreneHack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Okta Workspace MCP

No user-submitted related servers found.

    Related Servers

    • okta-auth

      bunizao
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Okta authentication, enabling AI agents to log in, check sessions, list, delete, and get cookies using saved Okta sessions.
      5
      4
      MIT

    • Okta-MCP

      vaibhavGoyal1096
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for Identity and Access Management with Okta integration, providing user and group management, audit logging, and permission guardrails.
      -

    • Okta MCP Server

      BalaGanaparthi
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for managing Okta users (CRUD operations) with full OAuth 2.1 compliance, enabling secure integration with Claude Desktop and other MCP clients.
      -

    • mcp-read-only-argocd

      lukleh
      A
      license
      A
      quality
      C
      maintenance
      A secure MCP server providing read-only access to Argo CD instances using browser session cookies, enabling querying of applications, projects, clusters, and repositories.
      14
      MIT

    • Okta MCP Server

      bangarrajuv2
      A
      license
      B
      quality
      C
      maintenance
      Exposes Okta incident-support and administrative workflows to MCP-compatible clients, enabling user investigation, group management, and system log queries.
      24
      87 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 23 tools

    Disambiguation3/5

    Several clusters have overlapping purposes, especially the auth/proof tools and identity/status tools such as whoami, userinfo, token-details, and okta-status. The descriptions are detailed enough to usually disambiguate, but similar names like my-apps vs list-apps and okta-browser-session-proof vs okta-browser-refresh-proof create some misselection risk.

    Naming Consistency2/5

    Naming conventions are mixed: some tools use okta-* prefixes, others are bare names like whoami, userinfo, and token-details, and admin tools follow list/get/search patterns. The okta-browser-* and okta-oauth-* subgroups are helpful, but the overall naming is not predictable.

    Tool Count3/5

    With 23 tools, the server is in the heavy range and covers a broad set of Okta workflows. The count is not unreasonable, but some tools could be consolidated, particularly around browsing, proof refresh, and identity lookup.

    Completeness3/5

    The authentication lifecycle and read-only directory access are well covered, including browser proofs, OAuth lab flows, userinfo, and user/group/app listing. However, there are notable gaps for an Okta workspace server: no create/update/delete operations for users, groups, or apps, and no token revocation or logout beyond reset/browser close.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources