F
licenseNot graded
qualityA
maintenanceEnables natural-language analysis of AWS cloud spending and Amazon Bedrock model invocation usage, including breakdowns by service, region, day, user, model, and cross-account data.
-
AWS Cost Explorer MCP Server
Officialby aws-samples
Related Servers
Alternatives to AWS Cost Explorer MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying of AWS spending and Amazon Bedrock usage data, with breakdowns by day, region, service, instance type, user, and model, including optional cross-account analysis.-
- FlicenseNot gradedqualityAmaintenanceEnables users to query and analyze AWS spending and Amazon Bedrock usage in natural language, with breakdowns by service, region, day, user, and model, including optional cross-account access.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language queries of AWS spending by service, region, day, and instance type, and of Amazon Bedrock usage from CloudWatch model-invocation logs, including optional cross-account cost analysis.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying of AWS cloud spending and Amazon Bedrock usage logs, with detailed breakdowns by day, region, service, instance type, user, and model, including cross-account cost retrieval.-
- FlicenseNot gradedqualityAmaintenanceEnables querying AWS spend data via Cost Explorer and Amazon Bedrock usage data from CloudWatch logs using natural language. Supports cross-account access, local and remote deployment, and integration with Claude Desktop and LangGraph agents.-
TDQS
C2.8/5.0
Scored across 4 tools
Disambiguation3/5
The tools have some overlap: get_bedrock_daily_usage_stats and get_detailed_breakdown_by_day both provide daily data, with the former being Bedrock-specific and the latter general. This could cause confusion about which tool to use for daily Bedrock costs. The hourly Bedrock tool and EC2 spend tool are distinct.
Naming Consistency2/5
Naming is inconsistent: 'get_bedrock_daily_usage_stats' and 'get_bedrock_hourly_usage_stats' follow one pattern, while 'get_detailed_breakdown_by_day' and 'get_ec2_spend_last_day' use different structures (e.g., 'by_day' vs 'last_day', 'usage_stats' vs 'breakdown' vs 'spend').
Tool Count3/5
With only 4 tools, the server feels under-scoped for a general 'AWS Cost Explorer' service. It covers only Bedrock and EC2, missing many other services and cost dimensions. However, for a focused subset, 4 tools could be reasonable.
Completeness2/5
The tooling covers only Bedrock daily/hourly stats, a generic daily breakdown, and EC2 daily spend. Missing other AWS services, monthly/forecast data, cost anomalies, tag-based queries, and broader exploration features. Significant gaps for a cost explorer tool.
Maintenance
ActivityInactive
ResponsivenessNo issues