Log inSubmit server
Climatiq logo

Climatiq

Searches Climatiq emission factors, estimates carbon emissions, and lists supported unit types through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Climatiq

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "climatiq": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-climatiq"
      ],
      "env": {
        "PLATFORM_CLIMATIQ_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Climatiq MCP server connects MCP clients to Climatiq’s emission-factor database and carbon estimate API. It provides tools for searching factors, calculating emissions from a selected factor and parameters, and listing unit types. Use it when an agent needs emission data or carbon estimates based on criteria such as category, region, year, or unit type. It can run through the Pipeworx gateway or locally as a stdio package.

Use cases

  • Search emission factors by region and category
  • Estimate carbon emissions from a selected factor
  • List valid unit types for an emissions workflow
  • Route environmental data questions through the Pipeworx gateway

Key features

  • Emission-factor search with filters
  • Carbon emissions estimation
  • Unit-type discovery
  • Remote MCP gateway access
  • Local stdio execution
  • Optional natural-language tool routing

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-climatiq (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads439Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Climatiq works

What Climatiq does

The Climatiq MCP server gives AI agents access to Climatiq’s emission-factor data API. Its tools support three focused tasks: finding relevant emission factors, estimating emissions with a chosen factor and input parameters, and listing available unit types.

Factor searches can be narrowed with fields including query text, category, source, region, year, unit type, page size, and page number. This makes the server suitable for workflows that need to identify an appropriate factor before calculating an estimate. The calculation tool accepts an emission factor and parameters, while the unit tool helps an agent discover valid measurement categories.

The integration is unofficial and is provided through Pipeworx. It belongs in the Environment & Nature category for applications that work with carbon accounting, emissions research, or environmental estimates.

How it works

The Climatiq MCP server can be reached in two ways. A remote MCP endpoint is available through the Pipeworx gateway at https://gateway.pipeworx.io/climatiq/mcp. The gateway exposes the Climatiq tools along with shared Pipeworx meta-tools, so tools/list may show more tools than the three specific to this package. The gateway’s initialization response is the authoritative source for the tools available at connection time.

A local package is also available through npm and communicates over standard input and output. The standalone mode exposes only the Climatiq pack’s tools and does not include Pipeworx routing or shared gateway meta-tools. HTTP callers can invoke tools directly through the gateway’s /v1/tools/ endpoints.

Setup and configuration

For a remote connection, add the gateway MCP URL to a client configuration. The README names Claude Desktop, Cursor, and Windsurf as supported setup targets. A full Pipeworx gateway URL is also available when an application needs all catalog packs listed directly.

The gateway can use the PLATFORM_CLIMATIQ_KEY environment variable for the platform credential. Local stdio use requires the @pipeworx/mcp-climatiq package and does not require a Pipeworx account.

Tools and capabilities

  • search_factors: searches emission factors with optional filters for query, category, source, region, year, unit type, result count, and page.
  • estimate_emissions: calculates an emissions estimate from an emission factor and supplied parameters.
  • list_unit_types: returns the available unit types.
  • ask_pipeworx: on gateway connections, lets an agent ask a natural-language question that the gateway routes to an appropriate tool.

The gateway may also expose shared discovery, search, memory, and other Pipeworx meta-tools. Those shared tools are not part of the standalone package.

Limitations and notes

The remote endpoint is a scoped gateway connection rather than a bare Climatiq-only MCP surface. Extra shared tool schemas may increase context usage, although they also allow routing to other Pipeworx catalog sources. The local package avoids those additional tools but does not provide cross-catalog routing.

The data source is Climatiq’s API at https://api.climatiq.io/data/v1/, accessed with a bearer token. Results and estimates therefore depend on the selected emission factor, supplied parameters, and the upstream data available through that API. The project is independent of, and not endorsed or published by, the upstream provider.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Climatiq

Climatiq is an MCP server that connects AI clients to Climatiq's emission-factor data API through the Pipeworx gateway or a local stdio package. Its main tools search factors, estimate emissions from a selected factor and parameters, and list supported unit types. It is an unofficial integration.

Install it locally by configuring an MCP client to run `npx -y @pipeworx/mcp-climatiq`. For remote use, point the client at `https://gateway.pipeworx.io/climatiq/mcp`.

Yes, Climatiq works with Cursor through the remote Pipeworx MCP URL. Add `https://gateway.pipeworx.io/climatiq/mcp` to Cursor’s MCP configuration.

Use the gateway credential through `PLATFORM_CLIMATIQ_KEY`, or provide a Climatiq key with the `?_apiKey=<key>` query parameter. Local stdio mode does not require a Pipeworx account.

Related MCP servers

All in Environment & Nature All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClimatiq AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/climatiq?style=directory)](https://allmcps.com/mcp/climatiq)
HTML Embed
<a href="https://allmcps.com/mcp/climatiq"><img src="https://allmcps.com/api/badge/climatiq?style=directory" alt="Climatiq on AllMCPs" /></a>