mcp and aws-finops-mcp-server
These are ecosystem siblings: the official AWS MCP servers provide foundational AWS service integrations, while the FinOps-specific server builds specialized cost analysis capabilities on top of the MCP protocol standard they both implement.
About mcp
awslabs/mcp
Official MCP Servers for AWS
Provides specialized MCP servers for AWS services including documentation access, infrastructure-as-code tools (CloudFormation, Terraform), databases, AI/ML services, and cost management—designed to integrate with AI coding assistants (Kiro, Cline, Cursor, Windsurf) and Claude Desktop via stdio transport. Enables LLM applications to access AWS context and perform authenticated API operations, with support for both local execution and remote deployment via AWS Lambda handlers.
About aws-finops-mcp-server
ravikiranvm/aws-finops-mcp-server
An MCP (Model Context Protocol) server that brings powerful AWS FinOps capabilities directly into your AI assistant. Analyze cloud costs, audit for waste, and get budget insights using natural language, all while keeping your credentials secure on your local machine.
Exposes AWS Cost Explorer and Budget APIs through two primary tools—`get_cost` for granular cost queries across services/tags/time ranges, and `run_finops_audit` for detecting infrastructure waste (stopped instances, unattached volumes, orphaned IPs)—while supporting multi-profile and multi-region queries via existing AWS CLI credentials. Implements the MCP stdio transport pattern, integrating natively with Claude Desktop and Amazon Q CLI as MCP clients, requiring only read-only IAM permissions (ce:GetCostAndUsage, budgets:ViewBudget, ec2:Describe*) with all credential handling delegated to local AWS CLI profiles.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work