No user-submitted related servers found.
Scored across 27 tools
The hierarchical resource paths make most tools clearly distinct, especially across providers, clients, domains, tenants, tenant providers, and policies. Some boundaries are still easy to confuse, such as provider clients' token creation versus tenant token validation, but descriptions provide enough context.
Tool names consistently use snake_case with a hierarchical resource path followed by a verb, such as providers_clients_list and tenants_providers_policies_create. Domain-specific verbs like add and verify are used appropriately without breaking the overall pattern.
The 27-tool surface is heavy for a single MCP server, but it is structured around CRUD operations for several nested resource types rather than arbitrary one-off tools. It is borderline appropriate for a multi-tenant provider/client/domain/policy domain, though still larger than ideal.
The server covers many core list/get/create/delete operations across providers, clients, domains, tenants, tenant providers, and policies. However, update operations are largely absent, and token lifecycle coverage is incomplete because there is token creation and validation but no token listing, revocation, or deletion.