lambda-cloud-mcp
Related Servers
Alternatives to lambda-cloud-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables agents to manage Lambda Cloud GPU instances over SSH, including executing commands, running background jobs, transferring files, and terminating instances, while also exposing UI-configured capacity alerts and auto-provisioning settings.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Hyperbolic's GPU cloud, allowing users to view available GPUs, rent instances, establish SSH connections, and run GPU-powered workloads through natural language commands.18MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to provision and terminate AWS EC2 instances using natural language commands.1-
- AlicenseNot gradedqualityBmaintenanceEnables Codex and other agents to discover live AutoDL GPU stock, produce cost- and time-optimized rental plans with human review, and manage approved Elastic/Pro deployments through the official API.5Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables LLMs to create, destroy, and manage AWS EC2 instances, including running commands via interactive shells.1-
- AlicenseAqualityCmaintenanceEnables AI agents to search Vast.ai GPU marketplace, deploy compute-heavy video models or ComfyUI, and guarantee instances are torn down after the job finishes.17MIT
TDQS
Scored across 8 tools
The tools are mostly distinct, each targeting a different resource such as images, regions, instance types, running instances, SSH keys, or file systems. The only potential confusion is between list_instance_types and cheapest_available_instance, since the former already includes price and capacity data, but their intents are still reasonably clear.
Most tools follow a consistent list_<resource> or get_<resource> pattern, making the naming predictable. cheapest_available_instance breaks this verb-first convention and would be more consistent as find_cheapest_instance or get_cheapest_instance.
Eight tools is well within the ideal range for a focused cloud-inspection server, and each tool has a clear purpose. The count feels appropriately scoped without unnecessary redundancy.
The tool set is heavily read-only, covering listing and getting resources but lacking any create, update, or delete operations. For a Lambda Cloud management server, the absence of launch/terminate instance operations and SSH key or file system creation is a significant gap that would prevent agents from taking meaningful actions.