Skip to main content
Glama
correaito
by correaito

Related Servers

Alternatives to Clerk MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables management of system users through a simple sample API, exposed as MCP tools for natural-language interaction.
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables secure MCP server functionality with Clerk authentication and user-specific API key management. Provides Next.js documentation tools through protected endpoints with multiple authentication methods including OAuth 2.1 with PKCE.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WorkOS User Management API. Enables Claude to manage users, organizations, memberships, invitations, and sessions in WorkOS.
      6 npm
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables user creation and retrieval through MCP tools, resources, and prompts, with Google Gemini integration for natural language interaction.
      1,026 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect to Authentik and securely query users, groups, applications, events, and system status, with an optional gated tool to enable or disable user accounts.
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: delete-user removes users permanently, list-users retrieves user data, lock-user blocks login access, and unlock-user restores it. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (delete-user, list-users, lock-user, unlock-user), using hyphen separation and clear action verbs. This uniformity enhances readability and predictability.

    Tool Count3/5

    With 4 tools, the count is reasonable for user management, but it feels slightly thin as it lacks create-user and get-user operations. This may limit full CRUD coverage, though the existing tools are well-scoped.

    Completeness3/5

    The tool set covers deletion, listing, locking, and unlocking users, which handles lifecycle management well. However, there are notable gaps: no create-user or get-user tools, which are essential for a complete user management surface, potentially causing agent workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues