Wattympc Server MCP Server

Model Context Protocol (MCP) server voor WattyEnergie - Nederlandse AI-native energievergelijker. Bereken energiekosten, vergelijk contracten en krijg dynamische prijzen via Claude, ChatGPT en andere AI assistenten. Exposed over MCP by the wattympc server mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• calculate_annual_energy_cost — - Bereken jaarlijkse all-in energiekosten inclusief belastingen
• compare_energy_deals — - Vergelijk alle Nederlandse energiecontracten
• get_dynamic_prices — - Actuele EPEX day-ahead elektriciteitsprijzen
• calculate_net_metering — - Bereken saldering voor zonnepanelen (2024-2030)
• get_supplier_list — - Overzicht Nederlandse energieleveranciers

Its toolset

Everything the assistant can do here goes through one of these:

• Endpoint — Beschrijving

Adding it to your client

@wattyenergie/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

• Node.js 18+ - Internet verbinding naar wattyenergie.nl API

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Wattympc Server's toolset — Endpoint — is a fair guide to whether it matches your workflow. It is maintained by brdev1990; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wattympc server mcp server does with a few real requests.