A
licenseC
qualityD
maintenanceEnables analyzing AWS cloud spending and Bedrock usage through natural language queries using Claude.
4
14
MIT No Attribution
Cloud FinOps Analyst MCP Server
by mihirkadam19
Related Servers
Alternatives to Cloud FinOps Analyst MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables users to query and analyze AWS cloud spending and Amazon Bedrock model usage through natural language, with breakdowns by day, region, service, instance type, user, and model, including cross-account cost visibility.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying of AWS cloud spending and Amazon Bedrock usage logs, with detailed breakdowns by day, region, service, instance type, user, and model, including cross-account cost retrieval.-
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of AWS cloud costs, waste audits, and budget insights across multiple profiles and regions.MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying of AWS spending and Amazon Bedrock usage data, with breakdowns by day, region, service, instance type, user, and model, including optional cross-account analysis.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying and analysis of AWS spending and model-invocation usage, including detailed breakdowns by service, region, account, day, and instance type.-
TDQS
A3.8/5.0
Scored across 10 tools
Disambiguation4/5
Tools are functionally distinct by cloud provider and action, but AWS tools lack a provider prefix (e.g., 'get_cost_summary' vs 'get_azure_cost_summary'), which could cause an agent to misselect if not reading descriptions carefully.
Naming Consistency3/5
The verb_noun pattern is consistent, but cloud prefixes are applied only to Azure and GCP tools (e.g., 'get_azure_idle_resources') while AWS tools are unprefixed ('get_idle_resources'). This inconsistency makes the naming pattern less predictable.
Tool Count5/5
10 tools is well within the ideal range for a FinOps server. Each tool covers a specific cloud provider and operation (cost summary, idle resources, anomaly detection), making the count appropriate for the domain.
Completeness4/5
The core FinOps surface (cost, waste, anomalies) is covered for AWS, Azure, and GCP, but tagging compliance is only available for AWS, leaving a notable gap for Azure and GCP users.
Maintenance
ActivityInactive
ResponsivenessNo issues