mcp/cost-explorer-mcp-server pulls statistics

AWS Cost Explorer MCP Server

Detailed cost analysis and reporting.

What is an MCP Server?

MCP Info

Attribute	Details
Docker Image	mcp/cost-explorer-mcp-server
Author	awslabs
Repository	https://github.com/awslabs/mcp

Image Building Info

Attribute	Details
Dockerfile	https://github.com/awslabs/mcp/blob/8f8460d377c692b27764daf20dfc3510706f98ca/src/cost-explorer-mcp-server/Dockerfile
Commit	8f8460d377c692b27764daf20dfc3510706f98ca
Docker Image built by	Docker Inc.
Docker Scout Health Score
Verify Signature	COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/cost-explorer-mcp-server --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
Licence	Apache License 2.0

Available Tools (7)

Tools provided by this Server	Short Description
get_cost_and_usage	[DEPRECATED] Retrieve AWS cost and usage data.
get_cost_and_usage_comparisons	[DEPRECATED] Compare AWS costs and usage between two time periods.
get_cost_comparison_drivers	[DEPRECATED] Analyze what drove cost changes between two time periods.
get_cost_forecast	[DEPRECATED] Retrieve AWS cost forecasts based on historical usage patterns.
get_dimension_values	[DEPRECATED] Retrieve available dimension values for AWS Cost Explorer.
get_tag_values	[DEPRECATED] Retrieve available tag values for AWS Cost Explorer.
get_today_date	[DEPRECATED] Retrieve current date information in UTC time zone.

---

Tools Details

Tool: get_cost_and_usage

[DEPRECATED] Retrieve AWS cost and usage data.

This tool retrieves AWS cost and usage data for AWS services during a specified billing period, with optional filtering and grouping. It dynamically generates cost reports tailored to specific needs by specifying parameters such as granularity, billing period dates, and filter criteria.

Note: The end_date is treated as inclusive in this tool, meaning if you specify an end_date of "2025-01-31", the results will include data for January 31st. This differs from the AWS Cost Explorer API which treats end_date as exclusive.

IMPORTANT: When using UsageQuantity metric, AWS aggregates usage numbers without considering units. This makes results meaningless when different usage types have different units (e.g., EC2 compute hours vs data transfer GB). For meaningful UsageQuantity results, you MUST be very specific with filtering, including USAGE_TYPE or USAGE_TYPE_GROUP.

Example: Get monthly costs for EC2 and S3 services in us-east-1 for May 2025 await get_cost_and_usage( ctx=context, date_range={ "start_date": "2025-05-01", "end_date": "2025-05-31" }, granularity="MONTHLY", group_by={"Type": "DIMENSION", "Key": "SERVICE"}, filter_expression={ "And": [ { "Dimensions": { "Key": "SERVICE", "Values": ["Amazon Elastic Compute Cloud - Compute", "Amazon Simple Storage Service"], "MatchOptions": ["EQUALS"] } }, { "Dimensions": { "Key": "REGION", "Values": ["us-east-1"], "MatchOptions": ["EQUALS"] } } ] }, metric="UnblendedCost" )…