Emission Factors vs Greencalculus MCP
A side-by-side look at the Emission Factors and Greencalculus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Emission Factors for environment & nature work as a local process; choose Greencalculus MCP 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?
Choose 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 Greencalculus MCP when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GREENCALCULUS_API_KEY, GC_API_KEY, GREENCALCULUS_MCP_URL, GREENCALCULUS_MCP_TIMEOUT_MS. - You want tools like
lookup_factor, lookup_factors, search_factors.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 55/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Not declared |
| Required env vars | EMISSION_FACTORS_API_BASE | GREENCALCULUS_API_KEYGC_API_KEYGREENCALCULUS_MCP_URLGREENCALCULUS_MCP_TIMEOUT_MS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 11 | 12 |
| Full listing | View Emission Factors | View Greencalculus MCP |
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)
Greencalculus MCP tools 12
lookup_factorFetch one emission factor by key, with its source and versionlookup_factorsFetch many factors by key in one call — a portfolio is one request, not one per factorsearch_factorsSearch the corpus by free textresolve_factorMap a messy real-world description to the best-matching factorexplain_absenceSay *why* a factor does not exist, rather than returning nothingcalculate_activityActivity → emissions, with unit conversion and GHG Protocol scopecalculate_electricityLocation-based and market-based electricitycalculate_embodiedEmbodied carbon (EN 15978), explicit about missing lifecycle stagescalculate_pcafPCAF financed emissions, with the audit trailcalculate_freightFreight by mode, distance and loadcalculate_spendSpend-based EEIOcalculate_business_travelBusiness travel across modes
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"
}
}
}
}
Greencalculus MCP
{
"mcpServers": {
"greencalculus-greencalculus-mcp": {
"command": "npx",
"args": [
"-y",
"greencalculus-mcp"
],
"env": {
"GREENCALCULUS_API_KEY": "YOUR_GREENCALCULUS_API_KEY_HERE",
"GC_API_KEY": "YOUR_GC_API_KEY_HERE",
"GREENCALCULUS_MCP_URL": "YOUR_GREENCALCULUS_MCP_URL_HERE",
"GREENCALCULUS_MCP_TIMEOUT_MS": "YOUR_GREENCALCULUS_MCP_TIMEOUT_MS_HERE"
}
}
}
}
Frequently asked questions
Emission Factors is categorized under Environment & Nature and uses a local stdio subprocess. Greencalculus MCP belongs to Environment & Nature and uses a local stdio subprocess. Pick Emission Factors for environment & nature work and Greencalculus MCP 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. Greencalculus MCP has no declared pricing — check the project's own site. Auth: api key required. 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 greencalculus-greencalculus-mcp 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. Greencalculus MCP has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.