GreenPick

Name: GreenPick
Author: bithug01

de bithug01versión 0.6.2i★ –iSe ejecuta en tu computadora

Nombre en el registroio.github.bithug01/greenpick

Instalar

Resumen

Descripción del creador (original en inglés)

Greener, cheaper cloud infra decisions — carbon + cost + latency tradeoffs, in-editor.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en tu computadora
Transporte: stdio
Categoría: Otros
Debes completar: EIA_API_KEY, ENTSOE_TOKEN, ELECTRICITYMAPS_TOKEN

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 1 de 1 superadas
Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
Debes completar tú: GREENPICK_CARBON_SOURCE, EIA_API_KEY, ENTSOE_TOKEN, ELECTRICITYMAPS_TOKEN, GREENPICK_CACHE_TTL_SECONDS, GREENPICK_LOG_LEVEL

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

PyPIuv de Python instalado (para el comando uvx)

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "greenpick": {
      "command": "uvx",
      "args": [
        "greenpick"
      ],
      "env": {
        "GREENPICK_CARBON_SOURCE": "your-value",
        "EIA_API_KEY": "your-value",
        "ENTSOE_TOKEN": "your-value",
        "ELECTRICITYMAPS_TOKEN": "your-value",
        "GREENPICK_CACHE_TTL_SECONDS": "your-value",
        "GREENPICK_LOG_LEVEL": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add greenpick --env GREENPICK_CARBON_SOURCE=your-value --env EIA_API_KEY=your-value --env ENTSOE_TOKEN=your-value --env ELECTRICITYMAPS_TOKEN=your-value --env GREENPICK_CACHE_TTL_SECONDS=your-value --env GREENPICK_LOG_LEVEL=your-value -- uvx greenpick

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "greenpick": {
      "command": "uvx",
      "args": [
        "greenpick"
      ],
      "env": {
        "GREENPICK_CARBON_SOURCE": "your-value",
        "EIA_API_KEY": "your-value",
        "ENTSOE_TOKEN": "your-value",
        "ELECTRICITYMAPS_TOKEN": "your-value",
        "GREENPICK_CACHE_TTL_SECONDS": "your-value",
        "GREENPICK_LOG_LEVEL": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "greenpick": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "greenpick"
      ],
      "env": {
        "GREENPICK_CARBON_SOURCE": "your-value",
        "EIA_API_KEY": "your-value",
        "ENTSOE_TOKEN": "your-value",
        "ELECTRICITYMAPS_TOKEN": "your-value",
        "GREENPICK_CACHE_TTL_SECONDS": "your-value",
        "GREENPICK_LOG_LEVEL": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

GREENPICK_CARBON_SOURCE env
Carbon data source: 'auto' (US->EIA, EU->ENTSO-E, Canada->Hydro-Québec/IESO live), 'mock' (offline: typical monthly values from a year of real data), 'eia', 'entsoe', or 'electricitymaps'. Defaults t…
EIA_API_KEY secreto env
Free US EIA-930 grid data API key (optional; enables live US carbon).
ENTSOE_TOKEN secreto env
Free EU ENTSO-E grid data token (optional; enables live EU carbon + day-ahead forecast).
ELECTRICITYMAPS_TOKEN secreto env
Electricity Maps API token (optional; used when GREENPICK_CARBON_SOURCE=electricitymaps).
GREENPICK_CACHE_TTL_SECONDS env
Cache lifetime for fetched grid data, in seconds.
GREENPICK_LOG_LEVEL env
Logging level (DEBUG, INFO, WARNING, ERROR).

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub bithug01, dueña del repo
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
– No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
– No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
… Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

Más estrellas que el 0% de los otros 32433 servidores de esta categoría
Publicado en el registro más recientemente que el 98% de los otros 32433 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 32433 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro GreenPick?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: EIA_API_KEY, ENTSOE_TOKEN, ELECTRICITYMAPS_TOKEN

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.6.2) llegó al registro ayer.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses

Instalar

Remote Desktop Commander

de desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Se ejecuta en la nube★ 211Actualizado ayer

Instalar

Symantec Cloud DLP AIops

de AIops-tools

Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.

Se ejecuta en tu computadoraActualizado hoy

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

GreenPick

Write greener, cheaper cloud infrastructure — before you deploy.

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 — 19 tools. Live carbon for US (EIA-930), EU (ENTSO-E) and Canada (Hydro-Québec,

IESO — no key needed), 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. Offline or without API keys, falls back to clearly-labelled *typical* values:

this month's average for each grid, from a year of real data.

*The same 40-GPU-hour training run emits ~0.6 kg CO₂ in Stockholm vs ~17.5 kg in Sydney — a ~28× difference from region choice alone (typical October grids; Sydney on Ember's 2025 national figure, a lower bound for its coal-heavier state grid). 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](docs/demo.md) — 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, with a realistic fallback built from a year of real data — no API keys required to start.

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

IS: directional "greener choice" guidance for a developer picking a cloud region while building. Guidance, with tradeoffs stated.
IS NOT: audited carbon accounting, ESG/Scope-2 reporting, or a real-time scheduler. GreenPick does not claim GHG-Protocol or ISO compliance — that's what the paid data vendors (Electricity Maps, WattTime) provide. GreenPick is for *decisions*, not *disclosures*.

How it differs from what's out there

Measurement tools (Cloud Carbon Footprint, CodeCarbon, Kepler) report what you *already* emitted, *after* you deploy. GreenPick advises *before* — at the choice.
Cloud providers' own tools (AWS CCFT, Azure, Google's "Low CO₂" region labels) cover *one* cloud and show carbon alone. GreenPick is cross-cloud and weighs carbon against cost and latency so you see the tradeoff, not just a green badge.
CI/CD carbon tools act at merge time on a pipeline job. GreenPick works earlier, in the editor, across more decisions (scheduling, right-sizing, training/inference, egress & residency).
Grid-data SDKs (Electricity Maps, WattTime, GSF Carbon Aware SDK) are building blocks; GreenPick is the decision layer on top of that kind of data.

The combination — cross-cloud, carbon + cost + latency, at design time, in the editor, with backfire guards — is the part nothing else puts together.

Scope

Providers: AWS, GCP, Azure — 25 regions across the US, Europe, Canada, Asia and Australia.
Workloads: long-running web/API services, GPU training runs, and deferrable jobs (ETL / batch / backups) — placement and timing for each.
Carbon = grid carbon intensity by region (directional, point-in-time; live US + EU), plus a day-ahead forecast (EU) for forward-looking scheduling.
Cost = compute + egress ballpark (deterministic static table, apples-to-apples across clouds; never LLM-invented).
Latency = geographic estimate to a stated user location.
Efficiency levers: greener instance family (perf-per-watt), right-sizing (cost + carbon together), and a carbon-metric scaffold to track your app over time.
Guardrails: data-locality / egress backfire checks and cross-jurisdiction residency flags.
Free data only. No flow-traced consumption accounting; carbon forecast is relative, not absolute.

Roadmap: data-format/engine efficiency advice, sub-national grid zones, CI/CD integration. See docs/user-questions-backlog.md.

MCP tools

19 tools, grouped by what you're trying to do.

Pick a region

Tool	What it does
`compare_regions_tri_axis`	Rank candidate regions by carbon with cost + latency tradeoffs; recommend a pick, each axis rated R/Y/G. Pass `regions` to rank only the ones you'd actually consider.
`greener_alternative_to`	"You picked X — the greenest region within +N ms latency is Y (−Z% carbon, Δcost)." The core nudge.
`region_carbon_now`	Current gCO₂/kWh for a region, with source + timestamp + freshness — and, when live, whether that's cleaner, dirtier or about usual for that hour this month.

Time a job (scheduling)

Tool	What it does
`cleanest_hours_to_run`	Cleanest recent hours to time a deferrable job (ETL, backups, training), + % reduction. Pass `window_hours` for a job of known duration → cleanest contiguous window to start at.
`cleanest_time_of_day`	For a recurring job (nightly batch): the region's cleanest time of day, averaged across recent days. A daily pattern, not a 7-day weekly one.
`greenest_regions_on_average`	Which regions are cleanest on a typical day in a given month (or the whole year), ranked from last year's real data. Offline, no keys; a planning view, not today's grid.
`carbon_forecast`	Forward-looking: which upcoming hours will be cleanest, from the EU day-ahead wind+solar forecast (ENTSO-E). Relative ranking; US/uncovered zones degrade to the recent historical pattern.

Estimate a workload's carbon

Tool	What it does
`estimate_workload_carbon`	Rough kgCO₂/month for a workload in a region (an estimate, not a measurement).
`estimate_training_carbon`	Carbon of a GPU training run (TDP-based energy × live grid), with greener where (region ranking) + when (cleanest hours) — the two levers that compound for portable, deferrable training.
`estimate_inference_carbon`	Energy + CO₂ of an LLM inference workload, by model size class × output tokens × requests (× live grid). A low–high band; smaller size class is the big lever. Self-hosted-friendly; not a named-model leaderboard.

Efficiency & guardrails

Tool	What it does
`greener_instance_family`	A greener same-size family in the same region via perf-per-watt (newer generation / ARM Graviton-class does the same work on less energy).
`rightsizing_check`	Right-sizing (the #1 FinOps win) with a carbon twin: if you're over-provisioned, a smaller size cuts both cost and carbon → the right-sized target with monthly $ and kg CO₂ saving.
`offhours_check`	For dev/test/staging that doesn't need to run 24/7: the monthly $ and kg CO2 saved by running it only N hours a week. Compute only, directional.
`data_locality_egress_check`	Warn when running compute away from where your data lives backfires: directional egress $ + coarse transfer carbon, and whether a greener-region move is still a net win.
`migration_payoff`	Does moving the data to the compute's region pay off? Payback in months, one-off vs monthly egress and transfer carbon, net over 12 months. Egress only.
`region_move_justification`	A short paste-ready paragraph for a pull request or decision record, with the carbon, cost, latency and egress numbers and their quality labels. Says so if the move is not an improvement.
`serving_pattern_advice`	For a user-facing platform: serve from one region or several? Traffic-weighted latency + carbon, with the multi-region data-sync egress and cross-jurisdiction residency catches.

Instrument & understand

Tool	What it does
`carbon_metric_scaffold`	Emits paste-in instrumentation (Python) so your app reports its own estimated carbon over time — observable proxies × GreenPick's power model × live grid. Self-tracking, directional; not a runtime meter.
`explain_methodology_and_limits`	The assumptions and what GreenPick explicitly does not claim.

Data sources (free; swappable behind one interface)

EIA-930 (US balancing authorities) and ENTSO-E (EU zones) — live grid carbon, auto-routed by region. Both also drive cleanest_hours_to_run from recent hourly history.
Hydro-Québec (Montreal / Québec City regions) and IESO (Toronto regions) — live hourly generation by source, public, no key needed. Hydro-Québec figures arrive 1.5–6 h late, so the latest complete hour is used and its timestamp shown.
Typical — the offline default and fallback: for each region, this calendar month's average intensity and average hour-of-day profile (UTC), computed from 12 months of real hourly EIA-930 / ENTSO-E data (data/typical.json, refreshed by scripts/refresh_typical.py). Labelled quality: "typical" — a realistic norm, never presented as a current reading.
Annual — for Singapore, Tokyo, Mumbai/Pune and Sydney, where no free hourly data exists: the country's yearly lifecycle grid intensity from Ember (via Our World in Data, CC BY 4.0), with source and year (data/annual.json). Labelled quality: "annual_average"; fine for comparing regions, but carries no timing signal.
**Mock

Solo se muestra el principio; lee el resto en el repo

GreenPick

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Otrosi

Preguntas frecuentes

Alternativas

Spec Driven Development

Remote Desktop Commander

Symantec Cloud DLP AIops

README del creador

Features

Contents

Why this exists

What it is / is NOT

How it differs from what's out there

Scope

MCP tools

Pick a region

Time a job (scheduling)

Estimate a workload's carbon

Efficiency & guardrails

Instrument & understand

Data sources (free; swappable behind one interface)