Skip to main content
Glama
aws-samples

AWS Cost Explorer MCP Server

Official
by aws-samples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_REGIONNoAWS region for Bedrock logs. Default is 'us-east-1'.us-east-1
AWS_PROFILENoAWS profile name to use for credentials. If not set, uses default profile.
MCP_TRANSPORTNoTransport protocol for MCP (stdio or sse). Default is 'stdio'.stdio
BEDROCK_LOG_GROUP_NAMEYesThe name of the CloudWatch log group for Bedrock model invocation logs.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_bedrock_daily_usage_statsC
Get daily usage statistics with detailed breakdowns.

Args:
    params: Parameters specifying the number of days to look back and region

Returns:
    str: Formatted string representation of daily usage statistics
get_bedrock_hourly_usage_statsC
Get hourly usage statistics with detailed breakdowns.

Args:
    params: Parameters specifying the number of days to look back and region

Returns:
    str: Formatted string representation of hourly usage statistics
get_ec2_spend_last_dayB
Retrieve EC2 spend for the last day using standard AWS Cost Explorer API.

Returns:
    Dict[str, Any]: The raw response from the AWS Cost Explorer API, or None if an error occurs.
get_detailed_breakdown_by_dayB
Retrieve daily spend breakdown by region, service, and instance type.

Args:
    params: Parameters specifying the number of days to look back

Returns:
    Dict[str, Any]: A tuple containing:
        - A nested dictionary with cost data organized by date, region, and service
        - A string containing the formatted output report
    or (None, error_message) if an error occurs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
config://app
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Resources