Scalekit MCP Server
OfficialRelated Servers
Alternatives to Scalekit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with PingOne Advanced Identity Cloud environments through natural language, supporting user management, authentication theme customization, log analysis, and identity data queries with secure OAuth 2.0 authentication.5725 npm2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceOfficial MCP server for Skycloak (managed Keycloak) that enables managing clusters, realms, applications, identity providers, users, themes, exports, SIEM destinations, and webhooks through natural language, with OAuth or API key authentication.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceMCP server for managing Ory Kratos identities, sessions, and authentication flows, enabling AI assistants to perform identity management tasks via natural language.20 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Okta users, groups, applications, policies, and logs through natural language commands.Apache 2.0

GatewayMCPofficial
AlicenseCqualityCmaintenanceEnables AI coding and operational assistants to securely access company systems through a single MCP endpoint, with OAuth authentication, scoped resource grants, audit logging, secret isolation, and corporate memory.94Apache 2.0- AlicenseBqualityCmaintenanceEnables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.369 npmApache 2.0
TDQS
Scored across 35 tools
Most tools map cleanly to distinct resource+action pairs (e.g., list_environment_roles vs list_environment_scopes). A few pairs are easy to confuse, particularly list_environment_connections vs list_organization_connections, and update_mcp_server vs switch_mcp_auth_to_scalekit both touch Scalekit auth.
Tool names overwhelmingly follow a consistent verb_noun pattern in snake_case (list_*, create_*, update_*, remove_*, add_*, set_*, get_*). The few action verbs like switch_, generate_, enable_, and search_ still read predictably and don't break the convention.
35 tools is well above the 25+ threshold and feels heavy for a single server. Many operations are granular (e.g., separate add/remove/list tools for each URI type) and could be consolidated without losing clarity.
The surface covers environments, organizations, roles, scopes, connections, and MCP servers broadly, but lifecycle coverage is uneven: roles and scopes are create/list only, MCP servers have no delete, and there is no list for initiate login or post-logout URIs. These gaps are noticeable but agents can often work around them.