AWS FinOps MCP - VS Code Extension

MCP server for AWS cost management and financial operations - auto-configures for GitHub Copilot Chat

Features

🚀 Auto-Configuration - Automatically registers the MCP server when installed. No manual configuration needed.

💰 Cost Analysis - Get current month costs, costs by service, and cost forecasts directly in Copilot Chat.

📊 Resource Inventory - List EC2 instances, RDS databases, and S3 buckets.

💡 Cost Optimization - Get AWS Trusted Advisor cost optimization recommendations.

Installation

Install the extension from VS Code Marketplace
Ensure you have AWS credentials configured
Open GitHub Copilot Chat and start asking about your AWS costs!

Usage

Once installed, simply ask GitHub Copilot about your AWS costs:

Cost Analysis

"What are my AWS costs this month?"
"Which services are costing me the most?"
"Forecast my AWS costs for next month"

Resource Inventory

"List all my EC2 instances"
"Show me my RDS databases"
"How many S3 buckets do I have?"

Cost Optimization

"How can I reduce my AWS costs?"
"Are there any optimization recommendations?"

Available MCP Tools

Tool	Description
`get-current-month-costs`	Get AWS costs for the current month
`get-costs-by-service`	Get costs grouped by AWS service
`get-cost-forecast`	Get cost forecast for the next period
`list-ec2-instances`	List EC2 instances with details
`list-rds-instances`	List RDS database instances
`list-s3-buckets`	List S3 buckets
`get-cost-optimization-recommendations`	Get Trusted Advisor recommendations

Configuration

Access settings via Command Palette → AWS FinOps: Configure AWS FinOps MCP

Setting	Description	Default
`awsFinopsMcp.autoStart`	Auto-start MCP server	`true`
`awsFinopsMcp.logLevel`	Log level (error, warn, info, debug)	`info`
`awsFinopsMcp.awsRegion`	Default AWS region	(env variable)
`awsFinopsMcp.awsProfile`	AWS profile to use	(default profile)

Commands

Command	Description
`AWS FinOps: Configure AWS FinOps MCP`	Open configuration options
`AWS FinOps: Restart MCP Server`	Restart the MCP server
`AWS FinOps: Show Available Tools`	Show list of available MCP tools
`AWS FinOps: Open Documentation`	Open this documentation

Prerequisites

AWS Credentials

You need AWS credentials configured. The extension uses the standard AWS credential chain:

Environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)
AWS credentials file (~/.aws/credentials)
IAM role (when running on AWS)

Required IAM Permissions

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ce:GetCostAndUsage",
                "ce:GetCostForecast",
                "ec2:DescribeInstances",
                "rds:DescribeDBInstances",
                "s3:ListAllMyBuckets",
                "support:DescribeTrustedAdvisorChecks",
                "support:DescribeTrustedAdvisorCheckResult"
            ],
            "Resource": "*"
        }
    ]
}

Note: Trusted Advisor features require AWS Business or Enterprise support plan.

Architecture

┌─────────────────┐     ┌────────────────────┐     ┌─────────────────┐
│ GitHub Copilot  │────▶│ AWS FinOps MCP    │────▶│ AWS APIs        │
│ Chat            │     │ Extension          │     │ - Cost Explorer │
│                 │◀────│ (MCP Server)       │◀────│ - EC2           │
└─────────────────┘     └────────────────────┘     │ - RDS           │
                                                   │ - S3            │
                                                   │ - Support       │
                                                   └─────────────────┘

Development

Building from Source

# Clone repository
git clone https://github.com/your-org/mcp-aws-finops.git
cd mcp-aws-finops

# Build MCP server
npm install
npm run build

# Build extension
cd extension
npm install
npm run compile
npm run bundle-mcp

# Package extension
npm run package

Installing Locally

# Install the .vsix file
code --install-extension aws-finops-mcp-1.0.0.vsix

Troubleshooting

MCP Server Not Starting

Check Output panel → "AWS FinOps MCP" for error messages
Ensure AWS credentials are configured
Run AWS FinOps: Restart MCP Server command

AWS API Errors

Verify IAM permissions are correctly configured
Check if AWS region is properly set
Ensure network connectivity to AWS APIs

Trusted Advisor Not Working

Trusted Advisor features require:

AWS Business or Enterprise support plan
Region set to us-east-1

Contributing

Contributions are welcome! Please see the main repository for contribution guidelines.

License

MIT

AWS FinOps MCP

Gleidson FerSanP