Epa Emissions vs Next Devtools MCP

A side-by-side look at the Epa Emissions and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Epa Emissions logoEpa EmissionsEnvironment & Nature · Local subprocess (stdio)EPA Emissions MCP — wraps EPA Envirofacts REST API (free, no auth)59GoodAuth: not declaredNext Devtools MCP logoNext Devtools MCPDeveloper Tools · Local subprocess (stdio)Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.86ExcellentAuth: no auth required

Verdict: choose Epa Emissions for environment & nature work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Epa Emissions logoChoose Epa Emissions when

  • You need dedicated capabilities in the Environment & Nature domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like ghg_facility_emissions, ghg_emissions_by_sector, tri_facility_releases.
Explore Epa Emissions

Next Devtools MCP logoChoose Next Devtools MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like nextjs_index, nextjs_call, nextjs_docs.
Explore Next Devtools MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEpa Emissions logoEpa EmissionsNext Devtools MCP logoNext Devtools MCP
CategoryEnvironment & NatureDeveloper Tools
Quality signal59/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars0832
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 1 upvotes
Tools54

Tools & capabilities

Epa Emissions tools 5

  • ghg_facility_emissionsThe biggest greenhouse-gas-emitting facilities in a US state (EPA GHGRP), ranked by total CO2-equivalent emissions. Returns each facility's name, location, industry sector(s), and total metric tons CO2e. State-scoped (pass a state). Data lags ~1.5 years — latest full year is auto-selected (currently 2023) unless a `year` is given.
  • ghg_emissions_by_sectorTotal greenhouse-gas emissions by INDUSTRY SECTOR within a US state (EPA GHGRP) — answers 'which sectors emit the most in <state>'. Sectors: Power Plants, Refineries, Chemicals, Metals, Minerals, Pulp and Paper, Petroleum and Natural Gas Systems, Waste, etc. Returns each sector's total metric tons CO2e and facility count, ranked. State-scoped (pass a state); data lags ~1.5y so the latest full year (~2023) is auto-selected unless `year` is given.
  • tri_facility_releasesSearch EPA TRI toxic chemical release facilities by state, and optionally by COUNTY — "what toxic releases are reported in Harris County, Texas" is the shape these questions usually take. Returns facility location, county, type, and chemicals released with quantities in pounds.
  • tri_chemical_releasesTrack toxic chemical releases by chemical name and state. Returns quantities released to air, water, and land broken down by year.
  • tri_trendsAnalyze toxic release trends over time by state or chemical. Returns historical release data across years to identify patterns and changes.

Next Devtools MCP tools 4

  • nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.
  • nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).
  • nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
  • browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.

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.

Epa Emissions

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "epa-emissions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epa-emissions"
      ]
    }
  }
}

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Epa Emissions is categorized under Environment & Nature and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Epa Emissions for environment & nature work and Next Devtools MCP for developer tools.

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.

Epa Emissions has no declared pricing — check the project's own site. Next Devtools MCP 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 epa-emissions and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Epa Emissions has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.