GreenPick MCP server

GreenPick

Write greener, cheaper cloud infrastructure — before you deploy.

<!-- mcp-name: io.github.bithug01/greenpick -->

A design-time sustainability co-pilot that runs as an MCP server inside your vibe-coding environment (Cursor / Claude Code / Kiro). Ask it where to deploy, when to run a job, or how to right-size — and it answers with an honest carbon + cost + latency tradeoff, in-editor, in seconds. (It responds when you ask; auto-nudging on infra-code changes is on the roadmap.)

Status: working — 15 tools. Live carbon for US (EIA-930) and EU (ENTSO-E), cross-cloud cost

parity (Vantage-refreshed), per-axis R/Y/G ratings, carbon-aware scheduling + day-ahead forecast,

GPU-training and LLM-inference carbon, right-sizing, serving-pattern and data-locality/residency

checks — all shipped. Falls back to clearly-labelled mock data offline or without API keys.

The same 40-GPU-hour training run emits ~0.7 kg CO₂ in Stockholm vs ~19 kg in Sydney — a ~30× difference from region choice alone. Ask GreenPick and it surfaces that (with the cost and latency tradeoff) while you're still in the editor, before you commit.

▶ See the 5-minute demo — three scenarios with real tool output (training placement, the egress backfire, the forecast).

Features

• 🧮 Right-sizing that cuts cost and carbon together — the FinOps win with a carbon twin. The money saved is the reason to run it; the carbon comes free.
• ⏱ Carbon-aware scheduling — run deferrable jobs (ETL, batch, training) when the grid is cleanest, now or day-ahead. A decision you make for every recurring job.
• ⚡ GPU training & LLM inference carbon — estimate a run's footprint and the greener where + when; the size/placement choices that actually move the number.
• 🌍 Greener region picks — ranked by carbon, with the cost + latency tradeoff shown, not hidden.
• 🛡 Backfire guards — flags when a greener move loses to egress, or crosses a data-residency line.
• 🔌 Live US + EU grid data, honest mock fallback — no API keys required to start.

Contents

• Why this exists
• What it is / is NOT · How it differs
• Scope
• MCP tools
• Data sources
• Honest limitations
• Quick start
• FAQ
• Contributing
• License

Why this exists

The same web service emits very different CO₂ depending on which region it runs in, because electricity grids differ in carbon intensity. Existing tools either rank regions in the abstract, or measure carbon after you deploy. GreenPick does it at the moment you choose, and tells you what the greener choice costs you in latency and dollars — so you can accept or reject it with eyes open.

What it is / is NOT

Shortened. The full README is on GitHub.