Cloudeval AI
Related Servers
Alternatives to Cloudeval AI
AlicenseAqualityAmaintenanceLets you use Claude Desktop, or any MCP Client, to use natural language to accomplish things on your Cloudflare account.22,294 npm4,305Apache 2.0
Terraform MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceThe Terraform MCP Server is a Model Context Protocol (MCP) server that integrates seamlessly with Terraform Registry and HCP Terraform APIs, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.1,538Mozilla Public 2.0
Related Servers
- FlicenseDqualityDmaintenanceEnables read-only assessment of AWS environments by inventorying resources, running security and operational checks, and generating actionable reports with cost analysis. Designed for contractors with support for assume-role authentication using external IDs.10-
- AlicenseAqualityBmaintenanceCloudOps MCP is a read-only Model Context Protocol server that exposes normalized operational infrastructure context (logs, metrics, deployments, health) to AI agents through a small set of typed, bounded tools.6MIT
- AlicenseAqualityAmaintenanceSelf-hosted MCP engine for private code reviews, providing deterministic static analysis and AST-level search over diffs, with findings passed to a review agent of your choice.52AGPL 3.0
- FlicenseAqualityCmaintenanceAI-powered code review tool that detects AI-generated code defects invisible to traditional linters — hallucinated packages, deprecated APIs, cross-file contradictions, hidden security anti-patterns, and over-engineering. Works as a standalone CLI, GitHub Action, or MCP server. Supports TypeScript, Python, Java, Go, and Kotlin. Free for individuals, no API key required.440-
- FlicenseNot gradedqualityCmaintenanceA read-only MCP server for inspecting AWS resources, detecting misconfigurations, and estimating costs across EC2, S3, and IAM, enabling agents to safely query and analyze cloud infrastructure.-
- AlicenseNot gradedqualityCmaintenanceEnables natural language analysis of AWS costs, automated FinOps waste audits, and budget monitoring across multiple profiles and regions while keeping credentials secure locally.184MIT
TDQS
Scored across 45 tools
Most tools are clearly separated by resource domains such as projects, reports, billing, sessions, credentials, and recipes. A few pairs could be confused—capabilities_get vs identity_get and status vs auth_status vs doctor—but the descriptions provide enough context to choose correctly.
The dominant pattern is <resource>_<operation>, e.g. projects_list, projects_get, sessions_search, credentials_inspect. Minor deviations like config_profiles, billing_ledger, status, and doctor break the pattern slightly, but overall the naming is predictable and readable.
With 45 tools, this is well beyond the 15-25 range that would still feel manageable. The high count comes from many read-only subdomains, but the sheer number makes tool selection and discovery heavier than necessary.
The read-side coverage is broad: projects, reports, billing, sessions, connections, credentials, recipes, and configuration are all represented. However, the surface is almost entirely read-only with no create, update, delete, execute, or configuration-changing tools, leaving significant lifecycle gaps for agents that need to take action.