@krovacloud/mcp
OfficialRelated Servers
Alternatives to @krovacloud/mcp
- FlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with your AWS environment. This allows for natural language querying and management of your AWS resources during conversations. Think of better Amazon Q alternative.13296-
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnterprise-grade MCP server integrating Claude AI capabilities, enabling AI-powered conversations, file operations, and system tools via the Model Context Protocol.1Apache 2.0
- FlicenseNot gradedqualityFmaintenanceAn MCP server that enables Claude to generate and execute AWS CLI commands, allowing users to manage AWS resources through natural language conversations.2-
- AlicenseNot gradedqualityBmaintenanceMCP server that bridges ChatGPT Plus/Pro to Claude Code, enabling chat, deep research, and image generation via your own account.163 PyPI51MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows Claude Code to interact with the OpenAI Codex CLI.17 npm21MIT
- AlicenseAqualityDmaintenanceMCP server that integrates OpenClaw AI assistant with Claude Code, enabling chat, task management, messaging, memory, alerts, agent spawning, and web search through configurable tools.12284 npmMIT
- AlicenseAqualityBmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.31872 npm920MIT
TDQS
Scored across 37 tools
Most tools target a distinct resource+action pair (cubes, domains, snapshots, webhooks, TCP mappings, backups, shares). A few are close—get_cube vs get_cube_ssh, and the cluster of share/backup-share tools—but descriptions draw clear boundaries and tell the agent when to use each.
Nearly everything follows a consistent snake_case verb_noun pattern (list_cubes, create_domain, delete_snapshot). Minor deviations like get_cube_ssh, get_domain_records, and power_off_cube add a qualifier, but the overall convention is readable and predictable.
37 tools is heavy for a single server, above the typical 3-15 sweet spot. However the platform genuinely spans many resource families (compute, networking, DNS, backups, webhooks, billing), so most tools do earn their place rather than being redundant.
Cube lifecycle is thoroughly covered (create/get/list/delete, power/wake/restart/restore, protect/unprotect, ssh, snapshots) and backups/domains/webhooks have near-full CRUD. Gaps are minor: no update/resize for cubes, no update for snapshots or TCP mappings, and no get for a single domain.