Skip to main content
Glama
phildougherty

Infracost MCP Server

by phildougherty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Infracost 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
      27 npm
      MIT

    • CloudCost MCP Server

      JadenRazo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to parse multi-cloud infrastructure-as-code files, query real-time pricing from AWS, Azure, and GCP, and generate cost estimates and comparison reports.
      494 npm
      MIT

    • kubopt

      kubeopt
      A
      license
      A
      quality
      A
      maintenance
      Kubernetes cluster cost analysis and optimization. Query costs, find savings opportunities, get rightsizing recommendations, and analyze pod spend across AKS, EKS, and GKE — directly from Claude
      6
      12
      Apache 2.0

    • 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.
      -

    • 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
      -
    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

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. The breakdown, diff, output, upload, and comment tools handle different stages of cost analysis workflows, while the cloud tools are neatly organized into guardrail and tagging policy categories with full CRUD operations. The naming and descriptions make it easy to distinguish between local CLI operations and cloud management functions.

    Naming Consistency5/5

    All tools follow a consistent snake_case naming pattern with a clear prefix structure: 'infracost_' for core tools and 'infracost_cloud_' for cloud-specific operations. Within each category, verbs like create, get, list, update, delete are used predictably, making the toolset highly readable and organized.

    Tool Count4/5

    With 16 tools, the count is slightly high but reasonable for the server's dual purpose of local cost analysis and cloud management. It covers both domains thoroughly without feeling excessive, though it might be borderline for some users. The tools are well-scoped, with each serving a distinct function in the Infracost ecosystem.

    Completeness5/5

    The toolset provides complete coverage for the Infracost domain, including local cost breakdowns, comparisons, formatting, uploading, and commenting, plus full CRUD operations for cloud guardrails and tagging policies. There are no obvious gaps; agents can perform all expected workflows from analysis to cloud integration and policy management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources