AWS DR Cost Estimator MCP Server
OfficialRelated Servers
Alternatives to AWS DR Cost Estimator MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of AWS cloud costs, waste audits, and budget insights across multiple profiles and regions.MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language queries of AWS spend and Bedrock usage data, providing detailed breakdowns by service, region, account, user, instance type, and model, including cross-account cost analysis.-
- AlicenseNot gradedqualityDmaintenanceEnables users to analyze AWS costs, track spending trends, and detect anomalies directly within Claude Desktop using the AWS Cost Explorer API. It provides tools to identify major cost drivers and compare usage across different time periods through natural language queries.MIT
- FlicenseNot gradedqualityAmaintenanceEnables users to ask natural-language questions about their AWS cloud spending, retrieving granular cost breakdowns by day, region, service, and instance type, along with Amazon Bedrock model usage pulled from CloudWatch invocation logs. It also supports cross-account spend analysis by assuming a role in other accounts.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language analysis of AWS cloud spending by exposing Cost Explorer API functionality, including EC2, Bedrock, and per-service cost breakdowns by day, region, user, model, and instance type. It also retrieves Amazon Bedrock usage data from CloudWatch model invocation logs and can pull spend information from other accounts via assumed IAM roles.-
- FlicenseNot gradedqualityAmaintenanceEnables users to query and analyze AWS cloud spending and Amazon Bedrock model usage through natural language, with breakdowns by day, region, service, instance type, user, and model, including cross-account cost visibility.-
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing strategies, comparing all strategies, and analyzing a single strategy. The scope difference between compare and analyze is clear, so there is minimal risk of misselection.
All tool names follow a verb_noun pattern with snake_case, using 'dr_strategy' as the core noun. The only variation is singular vs plural, which is semantically appropriate and does not break the overall consistency.
With 3 tools, the server is tightly scoped to its purpose of DR cost estimation. Each tool covers an essential operation (list, compare, analyze) without redundancy or unnecessary bloat.
The tool set covers the full read-only lifecycle of DR strategy costing: discovering available strategies, comparing all, and drilling into a single strategy. No obvious CRUD or analysis gaps exist for the stated purpose.