Skip to main content
Glama
getnable

nable (finops-mcp)

by getnable
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nable (finops-mcp)

No user-submitted related servers found.

    Related Servers

    • AWS FinOps MCP Server

      ravikiranvm
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language analysis of AWS costs, automated FinOps waste audits, and budget monitoring across multiple profiles and regions while keeping credentials secure locally.
      182
      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

    • signalforge

      karthikeyGoli
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first MCP server that analyzes and compiles prompts for multiple LLM clients, detecting intent, missing context, and waste risks to generate cost-aware, task-specific prompts.
      9 npm
      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

    A4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are mostly distinct: connect_aws/azure/gcp target specific providers, while get_cost_summary, estimate_change_cost, check_ai_budget, and check_action_policy each have a clear purpose. Slight overlap exists between list_connected_providers and nable_setup_status, but descriptions clarify their triggers.

    Naming Consistency3/5

    Most tools use a lowercase verb_noun pattern (connect_aws, get_cost_summary, estimate_change_cost, check_ai_budget), but 'what_can_nable_do' and 'nable_setup_status' break the convention, and verb prefixes vary (connect, get, list, estimate, check). Still readable overall.

    Tool Count5/5

    10 tools is well-scoped for a FinOps assistant, covering provider connection, cost summary, cost preflight, policy checks, and onboarding. Each tool has a defined role without excessive overlap.

    Completeness4/5

    The set covers core workflows: connect providers, view costs, estimate change costs, and check policy/budget. Missing budget creation/update and more advanced cost analytics, but these are workable gaps given the read-only advisory nature of the server.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources