Eia MCP Gridsense vs Emission Factors
A side-by-side look at the Eia MCP Gridsense and Emission Factors 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 Eia MCP Gridsense for environment & nature work as a local process; choose Emission Factors 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 Eia MCP Gridsense when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EIA_API_KEY.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E Emission Factors | |
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 36/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | EIA_API_KEY | EMISSION_FACTORS_API_BASE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 11 |
| Full listing | View Eia MCP Gridsense | View Emission Factors |
Tools & capabilities
Eia MCP Gridsense tools
No tool names declared yet. Check the project README from the listing page.
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)
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.
Eia MCP Gridsense
{
"mcpServers": {
"eia-mcp-gridsense": {
"command": "uvx",
"args": [
"eia-mcp-gridsense"
],
"env": {
"EIA_API_KEY": "YOUR_EIA_API_KEY_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
Eia MCP Gridsense is categorized under Environment & Nature and uses a local stdio subprocess. Emission Factors belongs to Environment & Nature and uses a local stdio subprocess. Pick Eia MCP Gridsense for environment & nature work and Emission Factors 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.
Eia MCP Gridsense has no declared pricing — check the project's own site. Emission Factors is listed as free. Auth: no auth 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 eia-mcp-gridsense and emission-factors as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Eia MCP Gridsense has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Emission Factors has 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars.