S
stevensu04/eco-router-mcp
MCP server that helps AI agents pick the lowest-carbon cloud region for a workload.
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
checked 2026-11-14 — requires Node >=22 (LTS since Oct 2024); a note, not a failure.
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"stevensu04-eco-router-mcp": {
"command": "npx",
"args": ["-y", "eco-router-mcp"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"stevensu04-eco-router-mcp": {
"command": "npx",
"args": ["-y", "eco-router-mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio stevensu04-eco-router-mcp -- npx -y eco-router-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · stevensu04/eco-router-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 1 ★ · 23 sources · mcp
- Install
npx -y eco-router-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y eco-router-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
stevensu04/eco-router-mcp;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Eco Router MCP
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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 (claudedesktopconfig.json)
json
"mcpServers": {
"eco-router": {
"command": "npx",
"args": ["-y", "eco-router-mcp"],
"env": { "ELECTRICITYMAPSAPITOKEN": "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 ELECTRICITYMAPSAPITOKEN 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 |
| rankregions | Ranks regions by grid carbon intensity, optionally balanced against estimated latency from an origin. Supports providers, countries, maxLatencyMs, maxCarbonIntensity, carbonWeight, energyKwh and limit. |
| findcleanwindow | 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 ELECTRICITYMAPSAPITOKEN with forecast access. |
| listregions | 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 rankregions:
json
"countries": ["EU"],
"origin": { "lat": 50.11, "lon": 8.68 },
"maxLatencyMs": 40,
"energyKwh": 500
Example request to findcleanwindow 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
[x] MCP server skeleton over stdio
[x] Full AWS, Google Cloud and Azure region dataset with sources
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 (claudedesktopconfig.json)
json
"mcpServers": {
"eco-router": {
"command": "npx",
"args": ["-y", "eco-router-mcp"],
"env": { "ELECTRICITYMAPSAPITOKEN": "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 ELECTRICITYMAPSAPITOKEN 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 |
| rankregions | Ranks regions by grid carbon intensity, optionally balanced against estimated latency from an origin. Supports providers, countries, maxLatencyMs, maxCarbonIntensity, carbonWeight, energyKwh and limit. |
| findcleanwindow | 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 ELECTRICITYMAPSAPITOKEN with forecast access. |
| listregions | 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 rankregions:
json
"countries": ["EU"],
"origin": { "lat": 50.11, "lon": 8.68 },
"maxLatencyMs": 40,
"energyKwh": 500
Example request to findcleanwindow 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
[x] MCP server skeleton over stdio
[x] Full AWS, Google Cloud and Azure region dataset with sources
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/stevensu04-eco-router-mcp/)
- Source
- awesome · https://github.com/stevensu04/eco-router-mcp
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.