2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 16 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Watershed Climate through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

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

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Watershed Climate tool calls without waiting for prompts between steps. Connect 16 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Watershed Climate

Ask Cline: "Using Watershed Climate, help me...". 16 tools available

Why Use Cline with the Watershed Climate MCP Server

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

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Watershed Climate + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from Watershed Climate and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Watershed Climate tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Watershed Climate and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Watershed Climate for real-time status and let Cline generate hotfix patches based on the findings

Watershed Climate MCP Tools for Cline (16)

These 16 tools become available when you connect Watershed Climate to Cline 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 Cline

Ready-to-use prompts you can give your Cline 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 Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Watershed Climate + Cline FAQ

Common questions about integrating Watershed Climate MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Watershed Climate to Cline

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