midPoint MCP Server
Related Servers
Alternatives to midPoint MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for JumpCloud APIs with full OpenAPI-driven coverage, enabling endpoint discovery, operation invocation, and direct API requests while managing multi-tenant user tokens in Vault and guarding mutating tools.20MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Mobilerun platform, exposing tools for device control, workflow automation, task management, and platform operations via a stateless HTTP or stdio interface with bearer-token authentication and policy-based access control.1Apache 2.0
- AlicenseBqualityCmaintenanceMCP server for Argo CD that provides multi-environment profiles, SSO or API key authentication, application search with cache, and REST API tools from the bundled OpenAPI catalog.2610 npmMIT
- AlicenseBqualityCmaintenanceThe most comprehensive Azure DevOps MCP server & CLI — 13 tools, 82 actions, single Go binary.141Apache 2.0
- AlicenseAqualityAmaintenanceProduction-grade MCP Gateway in Go featuring dynamic OpenAPI tool registration, RBAC governance, in-flight PII/DLP redaction, and structured JSON audit logging.51MIT
- AlicenseAqualityBmaintenanceMCP server for safely inspecting and operating a local Caddy admin API. Provides read-only tools and dry-run mutations for config management.7MIT
TDQS
Scored across 39 tools
Most tools map to a distinct resource+action, but several clusters blur together: list_my_team vs list_my_teammates vs list_my_managers are three near-parallel 'who is around me' tools distinguished only by prose, get_my_access vs get_user_assignments return essentially the same data for self vs other, and search_users overlaps with search_objects (which explicitly includes users). assign_role vs request_role and claim/release/decide_work_item are well separated by their descriptions, which do heavy lifting to compensate.
Nearly everything follows a consistent snake_case verb_noun pattern (get_/list_/search_/create_/assign_/unassign_/claim_/release_/decide_/run_/suspend_/resume_/test_/recompute_/disable_/enable_). Only whoami and ping break the verb-first convention, and get_my_access/get_user_assignments mix in a possessive noun phrase, but all are readable and predictable.
At 39 tools this is well beyond a comfortable surface for an agent, and several tools are narrow variants (three 'my team/teammates/managers' lists, two access-listing tools, close/release/claim/decide work items). The domain is genuinely broad (identity admin plus self-service approvals), which explains the size, but the number is far past the 16-25 'heavy' mark and increases misselection risk.
Approvals (list/claim/release/decide/cancel/get_case), tasks (list/get/run/suspend/resume/test) and self-service flows are covered end to end, but user lifecycle stops short of update_user and delete_user (no password reset either), and orgs are only reachable via the generic search_objects with no list_orgs/get_org, so common admin workflows have dead ends.