Skip to main content
Glama
aws-samples

AWS Cost Explorer MCP Server

Official
by aws-samples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to AWS Cost Explorer MCP Server

No user-submitted related servers found.

    Related Servers

    • Cloud FinOps Analyst MCP

      mihirkadam19
      A
      license
      A
      quality
      C
      maintenance
      Enables analyzing AWS cloud costs through natural language queries, providing cost summaries, anomaly detection, idle resource identification, rightsizing recommendations, and tagging compliance via Claude.
      10
      9 npm
      MIT

    • AWS FinOps MCP Server

      am2308
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language analysis of AWS cloud costs, waste audits, and budget insights across multiple profiles and regions.
      MIT

    • AWS Cost Explorer MCP Server

      aarora79
      A
      license
      C
      quality
      F
      maintenance
      A command-line interface and API that allows users to analyze and visualize AWS cloud spending data by enabling Claude to query AWS Cost Explorer through natural language conversations.
      4
      126
      MIT

    • AWS Cost Explorer MCP Server

      b-deepak
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying AWS costs and usage data from Claude Desktop through the Cost Explorer API.
      1
      -

    • AWS Billing MCP Server

      ankit8volt
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to analyze AWS costs, track spending trends, and detect anomalies directly within Claude Desktop using the AWS Cost Explorer API. It provides tools to identify major cost drivers and compare usage across different time periods through natural language queries.
      -
    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.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