finops-framework-mcp
Related Servers
Alternatives to finops-framework-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP-compatible AI clients to retrieve FinOps-aligned knowledge and runbooks on demand, covering cloud cost optimization across AWS, Azure, GCP, and OCI, AI inference economics, Kubernetes, data platforms, allocation, chargeback, anomaly management, and waste detection.663CC BY-SA 4.0
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to retrieve IT system status and search or rebuild a vector-indexed knowledge base of operational runbooks. It supports local, tool-grounded responses over stdio for Ollama-based agents, helping prevent hallucinated IT operations guidance.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to analyze AWS cloud costs, audit for waste, monitor budgets, and generate FinOps reports using natural language across multiple AWS profiles and regions, while keeping credentials on the local machine.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to analyze cloud spending by tags, time ranges, and service groupings, audit for waste such as stopped EC2 instances, unattached EBS volumes, and unassociated Elastic IPs, and check budget status across multiple accounts and regions using natural language, while keeping credentials securely on the local machine.-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to analyze AWS cloud costs, audit for waste, monitor budgets, and generate FinOps insights using natural language while keeping credentials local.-
- AlicenseNot gradedqualityCmaintenanceEnables 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
TDQS
Scored across 11 tools
Most tools target distinct entity types or actions, and descriptions explicitly steer users (e.g., get_maturity_assessment vs assess_maturity_path vs get_maturity_model). The maturity trio has some conceptual overlap, but the prose clarifies when to use each.
All names use consistent snake_case with clear verb_noun structure (get_*, list_*, search_*, assess_*, map_*). The pattern is predictable across the entire tool set.
11 tools is well within the ideal 3-15 range for a multi-entity framework browser. Each tool corresponds to a distinct entity type or workflow, with no excessive fragmentation.
The surface covers discovery, capabilities, KPIs, personas, maturity assessment/path/model, generic entities (principles, phases, domains, technology categories, scopes), and changelog. This is comprehensive read-only coverage for the FinOps Framework domain.