What is the workflow to upload activity data and get emissions calculated in Watershed?

The complete workflow is: (1) Use `create_upload` to create an upload container, (2) Use `upload_data_records` to add your activity data records (electricity, flights, shipping, etc.), (3) Use `validate_upload` to check data quality and fix any errors, (4) Use `submit_upload` to send data for emissions calculation, (5) Use `get_task_status` with the returned task_id to monitor processing. Once complete, your measurements appear in the inventory.

Can I check my organization's total carbon footprint for a specific year?

Yes! Use `list_inventories` to find your organization's GHG inventories by year. Then use `get_inventory` with the specific inventory_id to see the complete emissions breakdown by Scope 1 (direct), Scope 2 (energy), and Scope 3 (value chain). You can also use `list_measurements` with the year filter to see individual measurement details across all inventories.

Where do I find my Watershed API key and how do I generate one?

Log in to your Watershed dashboard at dashboard.watershedclimate.com, navigate to **Organization Settings** in the left menu, then go to the **API** section. Click to generate a new API key. Copy and save this key immediately — it won't be shown again. The key typically starts with `wh_`. Keep it secure as it provides full access to your organization's climate data.

What types of activity data can I upload to Watershed?

Watershed accepts a wide range of activity data including: electricity and energy consumption (kWh, therms), business travel (flights, hotels, rental cars), employee commuting, freight and shipping (ton-miles, kg-km), waste generated, water usage, and purchased goods/services. Each record needs fields like activity_type, quantity, unit, start_date, end_date, and optionally location and spend_amount for accurate emissions calculation.

Watershed Climate MCP Server for Claude Code 16 tools — connect in under 2 minutes

Name: Watershed Climate
Availability: InStock
Author: Vinkius

docs.anthropic.com/en/docs/claude-code

Built by Vinkius GDPR 16 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add Watershed Climate as an MCP server in one command and Claude Code will discover every tool at runtime — ideal for automation pipelines, CI/CD integration, and headless workflows via the Vinkius.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Watershed Climate and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·bash

# Your Vinkius token — get it at cloud.vinkius.com
claude mcp add watershed-climate --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Watershed Climate MCP Server

Connect your Watershed Climate organization to any AI agent and take full control of your carbon measurement, reporting, and reduction workflows through natural conversation.

Claude Code registers Watershed Climate as an MCP server in a single terminal command. Once connected, Claude Code discovers all 16 tools at runtime and can call them headlessly — ideal for CI/CD pipelines, cron jobs, and automated workflows where Watershed Climate data drives decisions without human intervention.

What you can do

Data Uploads — Create upload containers, add activity data records (electricity, travel, shipping), and validate data quality
Batch Data Ingestion — Upload multiple activity records in batch with proper formatting and emission factor mapping
GHG Inventories — List and inspect greenhouse gas inventories with Scope 1, 2, and 3 emissions breakdowns
Emissions Measurements — Query calculated carbon footprint measurements filtered by inventory or year
Processing Tasks — Monitor async processing tasks from upload submissions with real-time status checks
Reports & Disclosures — List and access generated sustainability reports (CDP, TCFD, custom formats)
Reduction Targets — View configured emissions reduction targets aligned with SBTi and net-zero commitments

The Watershed Climate MCP Server exposes 16 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Watershed Climate to Claude Code via MCP

Follow these steps to integrate the Watershed Climate MCP Server with Claude Code.

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

Add the MCP Server

Run the command above in your terminal

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

Start using Watershed Climate

Ask Claude: "Using Watershed Climate, show me..." — 16 tools are ready

Why Use Claude Code with the Watershed Climate MCP Server

Claude Code provides unique advantages when paired with Watershed Climate through the Model Context Protocol.

Single-command setup: `claude mcp add` registers the server instantly — no config files to edit or applications to restart

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

Claude Code runs headlessly, enabling unattended batch processing using Watershed Climate tools in cron jobs or deployment scripts

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

Watershed Climate + Claude Code Use Cases

Practical scenarios where Claude Code combined with the Watershed Climate MCP Server delivers measurable value.

CI/CD integration: embed Watershed Climate tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

Headless batch processing: schedule Claude Code to query Watershed Climate nightly and generate reports without human intervention

Shell scripting: pipe Watershed Climate outputs into other CLI tools for data transformation, filtering, and aggregation

Infrastructure monitoring: run Claude Code in a cron job to query Watershed Climate status endpoints and alert on anomalies

Watershed Climate MCP Tools for Claude Code (16)

These 16 tools become available when you connect Watershed Climate to Claude Code via MCP:

create_upload

An upload is required before you can add data records to Watershed. After creating an upload, you add data records to it, validate the data, and then submit it for processing. The upload acts as a batch grouping mechanism for related activity data. You can optionally provide a name and description to identify the upload purpose. Create a new data upload container in Watershed

delete_upload_data_record

Use this to remove incorrect or unwanted data before validating and submitting the upload. This action cannot be undone. The record_id is obtained from list_upload_data_records. Delete a specific data record from an upload

get_inventory

Use the inventory_id from list_inventories to inspect detailed carbon footprint results and understand your organization's emissions composition. Get detailed information about a specific GHG inventory

get_report

Use the report_id from list_reports to access the full report details including generated files, disclosure frameworks covered, and emissions data summarized. Reports are typically generated after inventories are complete and validated. Get detailed information about a specific report

get_task_status

When you submit an upload for processing, a task is created and returns a task_id. Use this tool to check if the processing is complete, still in progress, or failed. Task status is useful for monitoring large data submissions that may take time to process. Check status of a processing task (e.g., upload submission)

get_upload

Use the upload_id from list_uploads to inspect details before adding data or submitting for validation. Get details of a specific data upload

list_inventories

An inventory represents your organization's carbon footprint measurement for a specific year, containing Scope 1 (direct), Scope 2 (energy), and Scope 3 (value chain) emissions data. Each inventory has a year, status, and total emissions calculated from submitted activity data. List all GHG inventories in your Watershed organization

list_measurements

Measurements represent the actual carbon footprint values derived from your uploaded activity data. You can filter by inventory_id to see measurements for a specific year's inventory, or by year to see measurements across all inventories for that year. Each measurement includes the activity type, emission factor used, and calculated CO2e value. List emissions measurements with optional filters

list_reduction_targets

Reduction targets define your organization's goals for decreasing emissions over time, often aligned with Science Based Targets initiative (SBTi) or net-zero commitments. Each target includes baseline year, target year, reduction percentage, and progress tracking. List all emissions reduction targets configured in your organization

list_reports

Reports are formatted outputs of your climate data for disclosure, analysis, or internal review. Reports can include CDP disclosures, TCFD reports, or custom carbon footprint summaries. Each report has metadata about its type, generation date, and scope. List all available reports in your Watershed organization

list_upload_data_records

Each record contains the activity data that will be processed into emissions measurements. Use this to review the data before validating and submitting the upload. List all data records in a specific upload

list_uploads

Uploads are containers for activity data that will be validated and processed into emissions measurements. Each upload can contain multiple data records representing activities like electricity usage, flights, or shipping. Use this to see all existing uploads and their IDs before adding data or submitting for processing. List all data uploads in your Watershed organization

submit_upload

This triggers Watershed's calculation engine to convert activity data into emissions measurements using appropriate emission factors. The upload must be validated successfully before submission. The response includes a task_id that can be used to track processing status via get_task_status. Processing may take some time depending on data volume. Submit a validated upload for emissions processing

update_upload_data_record

Use this to correct errors or modify activity data before validation and submission. The record_id is obtained from list_upload_data_records. The body should contain the complete updated record object with all required fields. Update a specific data record in an upload

upload_data_records

Each record represents an activity that generates emissions (e.g., electricity consumption, business travel, shipping). Records should follow Watershed's data format with fields like: activity_type, quantity, unit, start_date, end_date, location, etc. You can upload a single record or multiple records in a batch by providing an array of objects. Example record: { "activity_type": "electricity", "quantity": 1500, "unit": "kWh", "start_date": "2024-01-01", "end_date": "2024-01-31" } Upload activity data records to an existing upload container

validate_upload

Validation ensures data quality and prevents rejection during the submission phase. The response includes validation results with any errors or warnings that need to be addressed. Always validate before submitting to ensure successful processing. Validate data in an upload before submission

Example Prompts for Watershed Climate in Claude Code

Ready-to-use prompts you can give your Claude Code agent to start working with Watershed Climate immediately.

"List all our GHG inventories and show me the total emissions for 2024."

"Create a new upload called 'Q1 2024 Electricity Data', add these 3 records: electricity usage for NYC office (50,000 kWh), London office (35,000 kWh), and São Paulo office (28,000 kWh) for January 2024, then validate and submit it."

"Show me our reduction targets and current progress toward our net-zero goal."