Skip to main content
Glama
anmolratna

FinOps AI Copilot MCP Server

by anmolratna

Related Servers

Alternatives to FinOps AI Copilot MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for programmatic read-only access to RiseUp cashflow data, allowing AI assistants to retrieve budget information via natural language.
      2
      107 npm
      25
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.
      5
      5 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that provides visibility into Parallels Remote Application Server infrastructure, policies, and sessions through the RAS REST API. It enables AI assistants to query site settings, published applications, and license status without performing any modifications.
      41
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides an OAuth-protected, scoped, and audited MCP server that lets AI assistants safely query business data through a fixed set of tools without direct database access.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to safely query live Odoo 19 data with a defense-in-depth security layer, providing read-only tools for partners, sales, inventory, and finance.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP gateway that enables AI agents to retrieve business data (sales, appointments, clients, inventory, etc.) from the AURON Suite backend with role-based access control, audit logging, and rate limiting.
      MIT

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially vendor, wallet, and trend-specific tools. However, getDashboardMetrics and dailySummary overlap noticeably, and several specialized transaction-list tools (failed, pending, large, retried) partially duplicate what findTransactions could accomplish.

    Naming Consistency4/5

    All tool names use camelCase and follow a predictable noun/query pattern like failedTransactions, vendorPerformance, and walletBalance. The main deviation is that some names are verb-led (findTransactionById, getDashboardMetrics) while others are bare nouns or adjectives, which is still readable and consistent in style.

    Tool Count3/5

    At 19 tools, the server is on the heavy side of the typical well-scoped range. The count is justified by the breadth of FinOps analytics, but several specialized transaction-list tools could potentially be consolidated, making the overall surface feel slightly bloated.

    Completeness4/5

    The tool set covers transaction lookup, filtering, vendor and merchant performance, wallet history, daily summaries, and trend analytics—strong coverage for a read-only FinOps copilot. Minor gaps exist, such as no direct refund/chargeback-specific analytics or flexible custom date-range comparisons beyond preset periods.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues