Skip to main content
Glama
jasonwilbur

Cloud Cost MCP

by jasonwilbur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Cloud Cost MCP

No user-submitted related servers found.

    Related Servers

    • cloudprice-mcp

      Albaker-Group
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets Claude (or any MCP-compatible client) compare on-demand compute + storage pricing across AWS, Azure, and GCP in real time.
      14
      50 PyPI
      1
      MIT

    • Cost Management MCP

      knishioka
      A
      license
      B
      quality
      C
      maintenance
      An MCP server for unified cost tracking and analysis across AWS, OpenAI, and Anthropic. It enables users to query expenditures, compare costs across providers, and analyze usage trends through natural language.
      10
      MIT

    • nable (finops-mcp)

      getnable
      A
      license
      A
      quality
      A
      maintenance
      Local-first FinOps MCP server. Ask about your AWS, Azure, GCP, and SaaS costs in plain English. Anomaly detection, rightsizing, idle-resource cleanup, and Jira/Linear ticketing. Credentials never leave your machine.
      10
      18
      Apache 2.0

    • azure-cost-mcp

      MO2k4
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that gives Claude live access to Azure pricing and cost data — retail prices, VM comparisons, reservation analysis, architecture estimates, and actual subscription spend.
      9
      -

    • signal_foundry_mcp

      JhaNishant
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for monitoring competitor pricing pages, scraping pricing data into SQLite, and answering plain-language questions about pricing plans via Claude.
      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.7/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a specific combination of cloud provider and resource type (e.g., compare_compute, compare_egress, compare_storage, etc.), with no overlapping functionality. The descriptions clearly delineate their distinct purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., calculate_workload_cost, list_aws_regions, refresh_oci_pricing). The prefixes (get_, list_, compare_, refresh_) are semantically clear and uniformly applied.

    Tool Count2/5

    With 31 tools, the server exceeds the 25+ threshold considered too many for typical scope. While the breadth of cloud providers and resource types partially justifies this, many tools could be consolidated (e.g., unifying refresh_* tools or combining compare_* tools).

    Completeness5/5

    The tool set covers the full lifecycle of cloud cost estimation: compute, storage, egress, GPU, Kubernetes, migration savings, and data freshness. Missing aspects like specific database or network pricing are out of scope, making the surface complete for its intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources