Climatiq MCP

Climatiq MCP plugs the Climatiq API into Claude, letting you calculate carbon emissions for electricity use, travel, freight, and cloud computing without leaving your conversation. You feed it activity data (kilowatt-hours, flight distances, shipping weights), and it returns CO2 equivalents based on Climatiq's emission factor database. The API coverage is solid: electricity by grid region, flights by route, freight by mode and distance, even AWS and Azure compute by instance type. I'd reach for this when building ESG reports or embedding carbon accounting into workflows. Say you're drafting a travel policy and want to compare the emissions of London to New York by plane versus a hypothetical rail route. Or you're auditing cloud infrastructure and need per-instance CO2 estimates for a quarterly sustainability report. The MCP handles the API calls and unit conversions, so you're not context-switching to a web dashboard or writing your own integration. The quirks are manageable. You need a Climatiq API key, which has a free tier but caps at 100 requests per month. That's fine for ad hoc queries, tight for production workloads. The MCP doesn't cache results, so repeated queries for the same activity burn through your quota. Documentation in the repo is thin: you'll want Climatiq's own API docs open to understand which parameters each emission factor expects (region codes, fuel types, vehicle classes). Error messages from the API can be cryptic if you pass malformed data, and the MCP doesn't add much context. This isn't a tool for casual users. If you're not already thinking about carbon accounting or don't have a Climatiq key handy, the setup friction outweighs the benefit. But for sustainability teams, carbon-aware developers, or anyone building ESG tooling, it's a clean way to pull emission data into Claude without writing a custom integration. The API is the real asset here; the MCP is a useful, if minimal, wrapper.