Skip to main content
Glama
bangarrajuv2

Okta MCP Server

by bangarrajuv2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Okta MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • Okta MCP Server (Remote)

      rittmananalytics
      A
      license
      Not graded
      quality
      C
      maintenance
      Wraps Okta's stdio MCP server to be accessible remotely via Streamable HTTP with OAuth authentication, and adds native Okta Admin API tools for application management.
      Apache 2.0

    • Okta MCP Server by CData

      CDataSoftware
      A
      license
      Not graded
      quality
      D
      maintenance
      This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Okta (beta): https://www.cdata.com/download/download.aspx?sku=KUZK-V&type=beta
      MIT

    • Okta MCP Server

      Zantonse
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates LLMs with Okta's Admin Management APIs, enabling natural language management of users, groups, applications, and more.
      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.2/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: get/retrieve vs list/search, and each focuses on a different Okta entity (application, group, user, policy, identity provider, network zone, system log, etc.). No two tools have overlapping purposes, even the aggregate incident summary tool combines existing data without conflicting with individual getters.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern prefixed with 'okta_': get for single entity retrieval, list for collections, and search for user-specific system logs. The naming is uniform down to singular vs plural (e.g., okta_get_application vs okta_list_applications) with no mixing of styles.

    Tool Count4/5

    With 24 tools, the set is on the higher end but still reasonable for a comprehensive Okta management server covering users, groups, applications, policies, identity providers, network zones, and system logs. It slightly exceeds the ideal 3-15 range but is not excessive given the domain complexity.

    Completeness2/5

    The tool set is entirely read-only: all tools are get/list/search operations with no create, update, or delete capabilities. This is a significant gap for a management API, as agents can inspect but not act on resources, leaving many workflows incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources