aws-billing-mcp
Related Servers
Alternatives to aws-billing-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables management and analysis of AWS security groups, S3 buckets, and VPC connections via MCP.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying AWS costs and usage data from Claude Desktop through the Cost Explorer API.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and analyze AWS costs and usage via the Cost Explorer API.MIT
- AlicenseNot gradedqualityCmaintenanceEnables analysis of AWS costs and usage through the AWS Cost Explorer API, supporting multi-account architectures with role assumption and cost comparison, forecasting, and anomaly detection.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAWS Cost Explorer + Anomaly Detection exposed as MCP tools. Surface unusual spend by service/account/tag, pull cost breakdowns, forecasts, savings recommendations. Read-only IAM — refuses to start if the role can modify resources. Curated by Archimedes Market with a verified Trust Report.MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying AWS Cost and Usage Report data via Amazon Athena for cost-effective and detailed cost analysis.1MIT
TDQS
Scored across 7 tools
Each tool serves a distinct purpose: querying cost/usage, discovering dimension values, forecasting, detecting anomalies, listing budgets, managing cost allocation tags, and checking commitment utilization. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case, using retrieval verbs like get_ and describe_. The pattern is uniform across the set, making it predictable for an agent.
With 7 tools, the server is well-scoped for its purpose of AWS billing and cost analysis. Each tool addresses a key aspect of cost management without being bloated or sparse.
The tool surface covers the core cost management workflows: historical analysis, forecasting, anomaly detection, budget tracking, tag discovery, and commitment utilization. There are no obvious dead ends or missing critical operations for a read-only billing server.