For energy retailers running powercloud

A powercloud MCP server that answers from contracts and payments under each user's own rights

A powercloud MCP server gives Claude, ChatGPT or Copilot named tools for contracts, meter points and unallocated payments. Hansen describes open APIs for the SaaS platform but publishes no reference, so access is agreed with Hansen first. Hansen ships no powercloud MCP server as of 21 September 2026; Pexon builds one.

Why powercloud is hard for agents

Where a powercloud connection needs engineering, not configuration

01 · Docs

API access goes through Hansen

There is no public API reference. Access runs through Hansen and its partner certification programme, so the blueprint starts with what your tenant is allowed to call.

02 · SaaS

No database, only the vendor's APIs

powercloud is multi-tenant SaaS, so there is no database to read. Every tool goes through Hansen's APIs and whatever rate and tenant rules apply to them.

03 · Vendor

Two changes of owner and name

Hansen acquired powercloud in 2024 and renamed the company in July 2025, while the platform kept its name. Contracts and contacts may now sit with Hansen, while older documents still say powercloud.

04 · Data

Billing and market data are regulated

The platform holds billing, payment and market communication data. Writes stay behind a person's confirmation, and no tool sends a market message.

Checked 21 September 2026

powercloud at a glance: interfaces, access and what exists for AI

	What we found
Interfaces	powercloud open APIs (not published, docs not published): Hansen describes open APIs and event-driven, cloud-native microservices; no public API reference or developer portal found; SaaS only · Certified partner interfaces (not published, docs behind customer or partner login): interfaces for certified partner apps such as forecasting, payment and EV charging, available through the partner programme · Analytics platform (reporting, docs not published): more than 30 standard reports in Power BI or Amazon QuickSight; a reporting source, not an API
Authentication	Not documented publicly. Check with Hansen which API access and credentials your tenant can get.
Vendor MCP server	No vendor server. No Hansen or powercloud MCP server found; the product's AI is limited to payment allocation.
Vendor AI assistant	AI-supported payment allocation, for which Hansen states a success rate above 98 percent.
Other connectors	A Salesforce Energy & Utilities integration exists as a MuleSoft Exchange asset; it is tied to Salesforce and MuleSoft, and its scope could not be read.

Hansen Technologies Germany GmbH (formerly powercloud GmbH), part of Hansen Technologies (DE). Energy retailers and municipal utilities in the DACH region running cloud billing for electricity, gas, heat and water, with customers such as EWE, Berliner Stadtwerke, Elli and Audax Renovables.

What we build

A first powercloud tool list, written as the manifest your IT team signs

Hansen Technologies Germany GmbH (formerly powercloud GmbH), part of Hansen Technologies does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# powercloud-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  get_contract:              # customer or contract ID -> contract, product, status
    backend: confirmed in blueprint
    mode: read
  list_contracts_by_product: # product, end-date range -> contracts
    backend: confirmed in blueprint
    mode: read
  get_meter_point:           # meter point ID -> meter point data and readings
    backend: confirmed in blueprint
    mode: read
  list_unallocated_payments: # date -> payments that were not allocated automatically
    backend: confirmed in blueprint
    mode: read
  draft_payment_allocation:  # payment, target account -> proposed allocation for a person to confirm
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the powercloud response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

powercloud holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.

What the connector answers, and what it will not do

Questions it answers

What is the contract status and next bill date for customer X?
Which payments from yesterday could not be allocated automatically?
Show all contracts on product Y that end next month.

What it will not do

Read more than the asking user may read in powercloud; permissions come from the platform, not from the connector.
Allocate a payment or change a contract by itself: the only write tool returns a proposed allocation that a person confirms.
Replace the analytics platform: portfolio-wide reporting stays in the standard reports or a data warehouse.

When this is the wrong page

If the goal is dashboards across the whole customer base, the powercloud analytics platform or a data warehouse is the better place. A connector is right when Claude, ChatGPT or Copilot has to answer a question about one contract, meter point or payment, or combine powercloud with another system.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your powercloud owners and checks every backend against your release and licence. Week two tests whether a person's own powercloud permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.

What we need from you: a named powercloud administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.

Sources: Hansen: powercloud · ZfK: powercloud becomes Hansen (Jul 2025) · Wikipedia (de): Powercloud · powercloud: platform economy. Read 21 September 2026. Vendor documentation changes; verify against the current release.

Connectors for 100 source systems — the dated catalogue this page belongs to
Claude MCP server development — how we build an MCP server for any internal system

Questions powercloud teams ask before the first tool call

Does powercloud have its own MCP server?

Not as of 21 September 2026. The platform's AI is limited to payment allocation, and we found no MCP server from Hansen or anyone else. An MCP server for powercloud has to be built against the APIs Hansen makes available to your tenant.

Do we need extra Hansen licences or access for an AI connector?

Probably an agreement, yes: API access runs through Hansen and its partner certification programme, and there is no public developer portal. Check with Hansen what your contract covers; the blueprint answers this before any tool is built.

Can the assistant see data a user is not allowed to see in powercloud?

No. The connector runs each call with the asking person's own rights, never a shared account with wider access. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a powercloud connector cost?

The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Next step

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your powercloud administrator in the room if you like.