Emission Factors vs Carbon Interface
A side-by-side look at the Emission Factors and Carbon Interface MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
E
Emission FactorsEnvironment & Nature · Local subprocess (stdio)Keyless US grid carbon + power cost by ZIP: eGRID Scope 2, Scope 1 fuels, site ranking, clean hours55GoodAuth: no auth requiredVerdict: choose Emission Factors for environment & nature work as a local process; choose Carbon Interface for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
EChoose Emission Factors when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
EMISSION_FACTORS_API_BASE. - You want tools like
lookup_emission_factor, lookup_by_coordinates, lookup_batch.
Choose Carbon Interface when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
estimate_electricity, estimate_flight, estimate_vehicle.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E Emission Factors | |
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 55/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | EMISSION_FACTORS_API_BASE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 11 | 3 |
| Full listing | View Emission Factors | View Carbon Interface |
Tools & capabilities
Emission Factors tools 11
lookup_emission_factorEPA eGRID CO2e + full generation mix for a ZIPlookup_by_coordinatesSame, resolved from lat/lon via Census geocoderlookup_batchEmission factors for up to 100 ZIPs at oncecalculate_emissionsScope 2 CO2e for a ZIP + kWh, location-based and market-based (Green-e residual mix)hourly_intensityHourly grid carbon intensity (EIA-930, ~24h lag)plant_emissionsPlant emissions (EPA CAMD): facility summaries or unit-hour recordsutility_tariffUtility-specific tariff, not state average (OpenEI URDB)electricity_rateState-average retail rate by sector (EIA-861)compare_sitesRank 2-25 candidate sites on grid carbon, $/kWh and cleanest daily windowcleanest_hoursCleanest N-hour window of the day to run a flexible load, in local timecalculate_fuel_emissionsScope 1 CO2e for fuels burned on site (EPA GHG Emission Factors Hub)
Carbon Interface tools 3
estimate_electricityEstimate CO2 emissions from electricity usage. Returns carbon emissions in grams, kg, and metric tons. Example: estimate_electricity(500, "us", "kwh") for 500 kWh in the US.estimate_flightEstimate CO2 emissions from a flight. Provide number of passengers and flight legs (departure/arrival airport IATA codes). Returns per-passenger and total carbon emissions. Example: estimate_flight(2, [{"departure_airport": "SFO", "destination_airport": "JFK"}]).estimate_vehicleEstimate CO2 emissions from driving a vehicle. Provide distance and a vehicle model ID (from Carbon Interface). Returns carbon emissions in grams, kg, and metric tons. Example: estimate_vehicle(100, "7268a9b7-17e8-4c8d-acca-57059252afe9", "mi").
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Emission Factors
{
"mcpServers": {
"emission-factors": {
"command": "npx",
"args": [
"-y",
"github:rozetyp/emission-factors-mcp"
],
"env": {
"EMISSION_FACTORS_API_BASE": "YOUR_EMISSION_FACTORS_API_BASE_HERE"
}
}
}
}
Carbon Interface
{
"mcpServers": {
"carbon-interface": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-carbon-interface"
]
}
}
}
Frequently asked questions
Emission Factors is categorized under Environment & Nature and uses a local stdio subprocess. Carbon Interface belongs to Environment & Nature and uses a local stdio subprocess. Pick Emission Factors for environment & nature work and Carbon Interface for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Emission Factors is listed as free. Auth: no auth required. Carbon Interface has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add emission-factors and carbon-interface as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Emission Factors has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Carbon Interface has 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars.