# Climatiq [Health: Active]

**Category:** 🌳 Environment & Nature  
**Repository:** https://github.com/pipeworx-io/mcp-climatiq  
**GitHub Stars:** 0  
**npm Downloads (last month):** 439  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/climatiq

## Description
Climatiq MCP — carbon footprint calculator with emission factors

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "climatiq": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-climatiq"],
    "env": {
      "PLATFORM_CLIMATIQ_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PLATFORM_CLIMATIQ_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/climatiq/readme_