Skip to main content
Glama
mihirkadam19

Cloud FinOps Analyst MCP Server

by mihirkadam19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Cloud FinOps Analyst MCP Server

No user-submitted related servers found.

    Related Servers

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

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only AWS cost exploration, forecasting, and anomaly detection through natural language using user-connected IAM credentials.
      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 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
    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.8/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are functionally distinct by cloud provider and action, but AWS tools lack a provider prefix (e.g., 'get_cost_summary' vs 'get_azure_cost_summary'), which could cause an agent to misselect if not reading descriptions carefully.

    Naming Consistency3/5

    The verb_noun pattern is consistent, but cloud prefixes are applied only to Azure and GCP tools (e.g., 'get_azure_idle_resources') while AWS tools are unprefixed ('get_idle_resources'). This inconsistency makes the naming pattern less predictable.

    Tool Count5/5

    10 tools is well within the ideal range for a FinOps server. Each tool covers a specific cloud provider and operation (cost summary, idle resources, anomaly detection), making the count appropriate for the domain.

    Completeness4/5

    The core FinOps surface (cost, waste, anomalies) is covered for AWS, Azure, and GCP, but tagging compliance is only available for AWS, leaving a notable gap for Azure and GCP users.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources