Ask Your AI Assistant to Find Your AWS Waste
The FinOps skill your coding agent didn't know it was missing
There is a prompt that used to require a terminal, a configured AWS profile, and twenty minutes of waiting:
"Run a cost and carbon scan against my AWS account and tell me what I'm wasting."
As of today, you can just… ask. GreenOps Scan now ships an
MCP server — the same protocol that lets
Claude, Cursor, ChatGPT, and other AI assistants call external tools. Add one
line of config and your assistant gains a greenops_scan tool that runs the
full read-only scan and hands back findings ranked by dollars saved.
No dashboard to log into. No agent credentials to provision. No data leaving your machine — the scan runs locally, on the AWS credentials you already have.
What it actually does
Two tools are exposed:
greenops_targets— lists your detected AWS profiles, regions, and the scanner modules available (EC2, S3, RDS, ECS, EKS, Lambda, CloudFront, ECR, Bedrock, VPC endpoints, OpenSearch, CloudWatch, and more). The agent calls this first so it picks a valid profile instead of guessing.greenops_scan— runs the complete scan pipeline: credential validation, permission checks, parallel module scans, resource-tag enrichment, Cost Explorer billing context, and the savings-realism filter. Returns the summary plus the top findings — each with estimated monthly USD savings, CO₂ impact, severity, and a concrete recommendation.
It's the exact same engine as npx greenops-scan — same modules, same
filters, same numbers. If you've used the CLI, nothing about the results is
different. What's different is who can run it: now it's whoever is already
open in your editor, mid-conversation, one prompt away.
Set it up in 60 seconds
Add this to your MCP client config (claude_desktop_config.json,
.cursor/mcp.json, or your client's MCP settings):
{
"mcpServers": {
"greenops": {
"command": "npx",
"args": ["-y", "greenops-scan", "mcp"]
}
}
}
That's it. The server uses whatever credentials are already configured —
AWS_PROFILE, env vars, ~/.aws profiles, SSO. If greenops_targets shows
your profiles, you're done.
Then try it:
"Scan my
prodAWS profile in eu-west-1 and show me the top 3 waste findings by monthly savings."
Your assistant will call greenops_targets to confirm the profile exists,
run greenops_scan (heads up: scans take 1–5 minutes depending on account
size — the agent knows to wait), and come back with a prioritized list like:
- $1,240/mo — 3 unattached EBS volumes in eu-west-1 (critical)
- $860/mo — RDS instance at 8% CPU utilization, right-size candidate
- $430/mo — NAT Gateway processing 12 TB/mo to S3 — a Gateway VPC Endpoint would make it free
Every finding includes the remediation step, so the natural follow-up — "write the Terraform to fix the top one" — is already half-done.
Honest caveats
- You need AWS credentials configured already. The MCP server is a thin,
local wrapper — it doesn't hold keys, it borrows yours. If
greenops_targetsreturns no profiles, set upaws configureorAWS_PROFILEfirst. (The read-only profile guide is the safe way to do that.) - It's read-only. The scanner uses describe/list APIs only — it cannot modify, delete, or even see data inside your resources.
- Scans take minutes, not seconds. A full-account scan across modules is real API work. Be patient on the first run; the agent handles the wait.
- Free, closed source. Same deal as the CLI: free to use, credentials stay local, source isn't public.
Try it
The package is on npm now — greenops-scan@0.1.38 includes the MCP server:
npx -y greenops-scan@0.1.38 mcp
Or just add the config above and ask your assistant to scan your account. New to the tool? The free CLI and the full scanner documentation cover everything the MCP server exposes — it's the same engine underneath.
