Skip to main content
Glama
symeta

aws-billing-mcp

by symeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to aws-billing-mcp

No user-submitted related servers found.

    Related Servers

    • AWS FinOps MCP Server

      beatriza04180
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to query AWS cost and usage data, run waste and savings audits, and monitor budgets through natural-language prompts in MCP-compatible clients. It keeps AWS credentials local and supports multi-profile and multi-region analysis.
      -

    • AWS FinOps MCP Server

      wbishop20639
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to query and analyze AWS cloud costs, audit for waste, and monitor budgets through natural language in MCP-compatible AI assistants, while keeping AWS credentials local.
      -

    • AWS Cost Explorer and Amazon

      hara324
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language analysis of AWS spend through Cost Explorer and Amazon Bedrock usage via CloudWatch model invocation logs, with breakdowns by service, region, model, user, day, and instance type. It also supports cross-account cost retrieval and local or remote MCP transports.
      -

    • AWS FinOps MCP Server

      ursulaberg
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to query AWS cloud costs, run waste and savings audits, and check budget status in natural language across multiple accounts, profiles, and regions. Runs locally using existing AWS CLI credentials, keeping them on the user's machine while connecting to MCP-compatible AI clients.
      -
    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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources