Koskamo

Behind the Watt MCP

Provides AI agents with read-only access to verified behind-the-meter data center power data, including facilities, announcements, events, and research dossiers. It enables agents to retrieve snapshots, understand evidence semantics, and access provenance receipts without scraping.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Behind the Watt MCP logo, by Yaro KoretsCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Yaro Korets
MCP endpoint (Streamable HTTP)
https://mcp.behindthewatt.com/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 0 of 4 declare behavior hints · 0 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve verified data center facility details and provenance
  • Access third-party reported project announcements
  • Download operating fleet data for analysis
  • Check regulatory events and project changes

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
Behind the Watt 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

4 advertised

search_facilities
Advertised by the server during the last successful anonymous check.

Search BTW-verified behind-the-meter power facilities. Returns published facts and capacity; announcements are not included.

search_facilities input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "query": {
      "type": "string",
      "description": "Name, developer, offtaker, county or state text"
    },
    "state": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2,
      "description": "Two-letter US state code"
    },
    "min_mw": {
      "type": "number",
      "minimum": 0
    },
    "status": {
      "type": "string",
      "description": "Published facility status, for example operating"
    }
  }
}
get_facility
Advertised by the server during the last successful anonymous check.

Get one verified facility dossier including units, permits, quotes, source URLs, SHA-256 checksums and archived evidence links.

get_facility input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1
    }
  }
}
get_announcements
Advertised by the server during the last successful anonymous check.

Get the separately classified third-party reported project pipeline. These records are not BTW-verified operating capacity.

get_announcements input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1
    },
    "state": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2
    }
  }
}
get_dataset_summary
Advertised by the server during the last successful anonymous check.

Get the canonical dataset date, verified fleet totals, methodology, license and citation.

get_dataset_summary input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
264 ms
95th percentile latency
264 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 264 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http behind-the-watt-mcp https://mcp.behindthewatt.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add behind-the-watt-mcp --url https://mcp.behindthewatt.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable behind-the-watt-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "behind-the-watt-mcp": {
      "url": "https://mcp.behindthewatt.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "behind-the-watt-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.behindthewatt.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start behind-the-watt-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "behind-the-watt-mcp": {
      "type": "http",
      "url": "https://mcp.behindthewatt.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http behind-the-watt-mcp https://mcp.behindthewatt.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.behindthewatt.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "behind-the-watt-mcp": {
      "serverUrl": "https://mcp.behindthewatt.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Behind the Watt MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.