Skip to main content
Glama

Related Servers

Alternatives to cloud-finops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and, when scoped writes are enabled, manage cloud estate data—inventory, costs, recommendations, schedules, governance, and deployments—across AWS, Azure, and GCP through a hosted remote MCP endpoint.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query multi-cloud costs, inventory, waste, and commitments across AWS, GCP, Cloudflare, and OVH through read-only MCP tools.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query multi-cloud cost and usage data through a uniform read-only toolset, including cost summaries, trends, budgets, forecasts, and optimization recommendations.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables governed, read-only SQL analytics, hybrid RAG knowledge search, financial metric calculation, and database schema introspection through MCP, with role-based access control, audit logging, and AI observability.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to analyze cloud billing data in FOCUS format through natural language queries. Provides 36+ predefined cost analysis queries, custom SQL execution, and schema documentation for multi-cloud cost optimization and FinOps practices.
      12
      Apache 2.0

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    The set splits cleanly into two parallel families — reference/guidance tools (list_references, find_references, get_reference) and waste-pattern playbooks (list_playbooks, find_playbooks, get_playbook) — with list/find/get boundaries spelled out explicitly in each description. The only soft spot is get_live_figures, whose purpose (current values for figures quoted inside three named references) slightly overlaps with get_reference on those same guides.

    Naming Consistency5/5

    Every tool follows the same verb_noun convention with a consistent singular/plural split: list_* for enumeration, find_* for ranked search, get_* for single-item retrieval. The only mild irregularity is get_live_figures not pairing with a list_/find_ family, but it still reads as the same grammar.

    Tool Count5/5

    Seven tools is well within the ideal range and each one earns its place, forming a neat 3+3 matrix over two content types plus one live-data fetcher. There is no redundant or trivial tool in the set.

    Completeness4/5

    Discovery, ranked search, and whole-or-section retrieval are covered for both references and playbooks, with error payloads (suggestions, valid_values, available_sections) acting as recovery paths. Minor gaps: no dedicated tool for enumerating valid facet values or the list of guides with live figures, so an agent must trigger an error to learn them, and get_live_figures covers only three guides.

    Maintenance

    ActivityActive
    ResponsivenessLimited data