Britive MCP Serverofficial
F
licenseNot graded
qualityD
maintenanceEnables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.
1
-
@beyondidentity/mcp
OfficialRelated Servers
Alternatives to @beyondidentity/mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely query and manage Okta resources for IAM and security administration. It supports dual-mode operation for standard tool interaction or autonomous agent workflows with sandboxed code execution.5-
OneLogin MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables managing users, apps, roles, authentication, and security settings through natural language, providing comprehensive access to the OneLogin API.60 npm5MIT- FlicenseNot gradedqualityDmaintenanceEnables management of BeyondTrust Endpoint Privilege Management (EPM) through natural language, supporting policy, computer, user, group management, file inspection, audit monitoring, and admin access requests.1-
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to manage Okta organizations through the Okta Admin Management APIs, supporting user provisioning, group management, and more via natural language.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables natural language management of Okta organizations, allowing users to perform administrative tasks such as user management, group operations, and application monitoring through AI agents.Apache 2.0
TDQS
B3.1/5.0
Scored across 36 tools
Disambiguation2/5
The tool set contains many overlapping operations: users can be managed via native tools (create_user, update_user, delete_user) or SCIM tools (scim_create_user, scim_update_user, scim_delete_user); similarly for groups. An agent cannot easily tell when to use one versus the other, and there is no guidance in the descriptions. This creates significant ambiguity and risk of misselection.
Naming Consistency2/5
Most tools follow a verb_noun pattern (e.g., create_user, list_groups), but there are several deviations: some use get_ instead of list_ (get_groups, get_user), and the SCIM tools are prefixed with scim_ while others are not. Also, 'add_group_users' and 'delete_group_users' are less predictable. The mix of prefixes and inconsistent use of get/list reduces consistency.
Tool Count3/5
With 36 tools, the set is quite large and includes a duplicate SCIM and native API for similar operations, which bloats the surface. However, the domain (identity management with users, groups, passkeys, SCIM) is broad enough that many tools are justified. It borderline exceeds a manageable count, but each tool has a clear purpose.
Completeness3/5
The surface covers core CRUD for users, groups, passkeys, and SCIM resources, but there are notable gaps: no tool to update a passkey (e.g., rename or change state), no tool to manage applications or SSO connections despite being mentioned in search examples ('list applications', 'manage SSO'). Also, there is no explicit tool for listing or managing passkey bindings beyond creation and status retrieval. These gaps could hinder some workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues