Skip to main content
Glama
OptimNow

cloud-finops-mcp

by OptimNow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to cloud-finops-mcp

No user-submitted related servers found.

    Related Servers

    • ZopDev MCP by zopdev

      ZopDev MCPofficial

      zopdev
      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

    • cloud-tools

      munhq
      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

    • finops-mcp

      motoraif
      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

    • Enterprise MCP Knowledge

      Mudit-R
      F
      license
      Not graded
      quality
      B
      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.
      -

    • FOCUS MCP Server

      glassity
      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.
      132 PyPI
      12
      Apache 2.0
    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.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    The six tools form two clean triplets (references and playbooks), each split into list/find/get with distinct roles, and the descriptions explicitly steer callers between list_* and find_* based on whether filters are known. The only residual overlap is that list_references and find_references return the same payload shape and find with no filters behaves like list, but the guidance on when to use each is unusually clear.

    Naming Consistency5/5

    All six tools follow a strict verb_noun pattern (list_references, find_references, get_reference, list_playbooks, find_playbooks, get_playbook), and the verb choice is semantically consistent across both resource families. Plural for collection operations and singular for single-item fetches is applied uniformly.

    Tool Count5/5

    Six tools is well-scoped for a read-only guidance library: two resources times three access patterns, with no redundant or speculative endpoints. Every tool has a clear, earned place in the workflow.

    Completeness4/5

    Discovery (list), faceted search (find) and retrieval with section-level granularity (get) cover the read-only lifecycle for both references and playbooks, including miss-recovery via suggestions and available_sections. Minor gaps: no cross-corpus search spanning references and playbooks at once, and no standalone way to enumerate a reference's headings without triggering a section miss.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources