Skip to main content
Glama
aarora79

AWS Cost Explorer MCP Server

by aarora79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

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_dayC
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_dayC
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
system_prompt_for_agent Generates a system prompt for an AWS cost analysis agent. This function creates a specialized prompt for an AI agent that analyzes AWS cloud spending. The prompt instructs the agent on how to retrieve, analyze, and present cost optimization insights for AWS accounts. Args: aws_account_id (Optional[str]): The AWS account ID to analyze. If provided, the agent will focus on this specific account. If None, the agent will function without account-specific context. Returns: str: A formatted system prompt for the AWS cost analysis agent.

Resources

Contextual data attached and managed by the client

NameDescription
config://app
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.7/5.0

Scored across 4 tools

Disambiguation3/5

The tools have some overlap in purpose, particularly between the two Bedrock usage tools and the daily breakdown tool, which all involve daily cost/usage data. However, the descriptions clarify distinctions: get_bedrock_daily_usage_stats and get_bedrock_hourly_usage_stats focus on Bedrock service usage (daily vs. hourly), while get_detailed_breakdown_by_day covers broader cost breakdowns across services. The EC2 tool is distinct but limited to a single day.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (get_*_*) throughout, with clear action-object structure. Minor deviations exist, such as get_detailed_breakdown_by_day using 'by_day' instead of a noun like 'daily_breakdown', but overall the pattern is predictable and readable.

Tool Count2/5

With only 4 tools, the server feels under-scoped for an 'AWS Cost Explorer' purpose, which typically involves querying costs across multiple services, time ranges, and dimensions. The tools are narrowly focused on Bedrock and EC2, lacking coverage for other AWS services or flexible time-range queries, making the set feel incomplete for general cost exploration.

Completeness2/5

There are significant gaps in the tool surface for cost exploration. The server lacks tools for querying costs by service, region, or account over custom time periods, and it misses core operations like filtering, grouping, or forecasting. The tools are limited to specific services (Bedrock, EC2) and fixed time frames, which will cause agent failures when broader cost analysis is needed.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources