Scalekit MCP Server
OfficialRelated Servers
Alternatives to Scalekit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.5748 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.6 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Okta users, groups, applications, policies, and logs through natural language commands.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants like Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, with a hosted OAuth server or a local stdio package. Also supports generating MCP tools from any OpenAPI spec.3,386 npmMIT

GatewayMCPofficial
AlicenseCqualityFmaintenanceEnables 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
TDQS
Scored across 35 tools
Descriptions are highly cross-referential and explicitly state boundaries (e.g., list_environment_connections vs list_organization_connections vs list_connected_accounts; create_organization_user vs invite_workspace_member). A few near-duplicate read tools (redirect URI variants, connection types) could still trip an agent, but the boundaries are generally clear.
All 35 tools follow a consistent snake_case verb_noun pattern (list_, get_, create_, update_, remove_, add_, set_, enable_, search_, register_, etc.). No mixed conventions or vague names appear.
With 35 tools, this is a heavy, granular surface for the domain. Many operations are split into very specific tools (separate add/remove for each redirect URI type), which suggests overexposure rather than a lean, well-scoped set.
Coverage spans environments, organizations, users, SSO connections, OAuth connectors, MCP servers, and docs, but lifecycle operations are uneven. Several resources lack update/delete tools (e.g., organizations, users, roles, scopes, connected accounts, MCP servers), creating notable gaps for full CRUD workflows.