2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 16 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "watershed-climate": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Watershed Climate
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 Desktop is the definitive way to connect Watershed Climate to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 16 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Desktop 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 Desktop via MCP

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

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Watershed Climate

Look for the 🔌 icon in the chat — your 16 tools are now available

Why Use Claude Desktop with the Watershed Climate MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Watershed Climate through the Model Context Protocol.

01

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Watershed Climate + Claude Desktop Use Cases

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

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Watershed Climate MCP Tools for Claude Desktop (16)

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

01

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

02

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

03

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

04

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

05

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)

06

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

07

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

08

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

09

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

10

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

11

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

12

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

13

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

14

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

15

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

16

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 Desktop

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

01

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

02

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

03

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

Troubleshooting Watershed Climate MCP Server with Claude Desktop

Common issues when connecting Watershed Climate to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Watershed Climate + Claude Desktop FAQ

Common questions about integrating Watershed Climate MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.

Connect Watershed Climate to Claude Desktop

Get your token, paste the configuration, and start using 16 tools in under 2 minutes. No API key management needed.