Eco Router

Name: Eco Router
Author: stevensu04

@stevensu04MCP server · External

Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency.

Energyv0.1.1MITTypeScript

Freeno charge per call

How to install

Runs on your machine from its package; the steps are below.

What it does

Reads
Writes
High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmeco-router-mcpv0.1.1

Run

npx -y eco-router-mcp

MCP client config

{
  "mcpServers": {
    "eco-router": {
      "command": "npx",
      "args": [
        "-y",
        "eco-router-mcp"
      ]
    }
  }
}

README4 min readView on GitHub

Eco Router MCP

An MCP server that helps AI agents pick the lowest-carbon cloud region for a workload.

The same GPU job can emit several times more CO₂ depending on which grid powers the datacenter. Eco Router maps AWS, Google Cloud and Azure regions to the electricity grids they draw from, so an agent can ask:

"Where should I run this training job? Data must stay in the EU and latency should be under 150 ms."

and get back a ranked shortlist with the reasoning behind it.

Carbon figures are location-based grid averages. They describe the grid that supplies each region, not the renewable energy a provider buys, so regions in the same grid get the same value. See what the numbers represent.

Status: early release (v0.1). Corrections and feedback are welcome in issues. See Roadmap.

Install

Requires Node.js 22 or later.

Claude Code

bash

claude mcp add eco-router -- npx -y eco-router-mcp

Claude Desktop (claude_desktop_config.json)

json

{
  "mcpServers": {
    "eco-router": {
      "command": "npx",
      "args": ["-y", "eco-router-mcp"],
      "env": { "ELECTRICITY_MAPS_API_TOKEN": "optional" }
    }
  }
}

Live grid data (optional)

Out of the box, Eco Router uses annual averages (per grid in the US, per province in Canada, per country elsewhere), so it works with no setup. For hourly, grid-level data, set ELECTRICITY_MAPS_API_TOKEN to your own Electricity Maps API token. Zones your plan does not cover fall back to the annual average automatically.

Your use of live data is governed by your own Electricity Maps plan and its terms. At the time of writing, Electricity Maps offers free access for academic and personal non-commercial use, and a 14-day trial for commercial evaluation. Commercial use requires a paid license. Eco Router does not provide or share any token.

Tools

Tool	What it does
`rank_regions`	Ranks regions by grid carbon intensity, optionally balanced against estimated latency from an `origin`. Supports `providers`, `countries`, `maxLatencyMs`, `maxCarbonIntensity`, `carbonWeight`, `energyKwh` and `limit`.
`find_clean_window`	For flexible batch jobs, finds the start time in the next 72 hours with the lowest forecast carbon intensity in each grid zone, and the savings compared with starting now. Requires `ELECTRICITY_MAPS_API_TOKEN` with forecast access.
`list_regions`	Lists cloud regions and the grid zone each one draws power from. Filter by `provider` (`aws`, `gcp`, `azure`) or `country`.

countries accepts ISO 3166-1 alpha-2 codes and the groups EU and EEA.

Example request to rank_regions:

json

{
  "countries": ["EU"],
  "origin": { "lat": 50.11, "lon": 8.68 },
  "maxLatencyMs": 40,
  "energyKwh": 500
}

Example request to find_clean_window for a 6-hour job that must finish within two days:

json

{
  "countries": ["DE", "FR", "SE"],
  "durationHours": 6,
  "withinHours": 48,
  "energyKwh": 500,
  "timezone": "Australia/Brisbane"
}

Scoring, data sources and their limits are explained in docs/methodology.md.

How regions are mapped to grids, and which mappings rest on assumptions, is documented in docs/regions.md.

Roadmap

MCP server skeleton over stdio
Full AWS, Google Cloud and Azure region dataset with sources
Carbon data: published annual averages by default, live data with an optional Electricity Maps API token
rank_regions: rank regions by carbon intensity and estimated latency, with hard limits such as allowed countries or a carbon ceiling
US grid-level annual data without a token (EPA eGRID)
Canadian provincial annual data without a token (National Inventory Report)
Grid-level annual data for Australia
Time shifting: suggest when to run, using carbon forecasts
Publish to npm and the MCP Registry

Development

bash

npm install
npm test           # unit tests, no network needed
npm run typecheck
npm run build      # compiles to dist/
npm run dev        # runs the server over stdio from source
npm run update:baseline  # refreshes national averages from Ember
npm run update:egrid     # refreshes US grid averages from EPA eGRID
npm run update:canada    # refreshes Canadian provincial averages

Data sources

Annual carbon intensity: Ember, Yearly Electricity Data, licensed under CC BY 4.0.
US grid generation mix: US EPA eGRID (public domain), converted to lifecycle emissions with Ember's US factors.
Canadian provincial generation mix: Environment and Climate Change Canada, National Inventory Report, Annex 7, converted to lifecycle emissions with Ember's Canadian factors. Contains information licensed under the Open Government Licence – Canada.
Live carbon intensity (optional): Source: ElectricityMaps.com, using your own API token and subject to the terms of your plan.
Region lists: official AWS, Google Cloud and Azure documentation. See docs/regions.md.

Contributing

Corrections to region data are especially welcome. See CONTRIBUTING.md to get started.

Credits

Eco Router started as a hackathon project. Thanks to the original team for the scoring design this project builds on: Chris (@chrislee021225), Joli (@L-Joli), Bob (@Loic0927), Irene Tsai (@YunTong09) and Steven Su (@stevensu04).

License

MIT

Similar modules

Browse Energy