For utilities running kVASy

A kVASy MCP server that answers from contracts, meters and invoices under each user's own rights

A kVASy MCP server gives Claude, ChatGPT or Copilot named tools for contracts, meter readings, invoices and instalments in SIV's utility ERP. SIV names web service interfaces but publishes no API reference, so the interfaces are confirmed with SIV first. SIV ships no kVASy MCP server as of 21 September 2026; Pexon builds one.

Why kVASy is hard for agents

Where a kVASy connection needs engineering, not configuration

01 · Docs

No public interface reference

SIV does not publish its API documentation. The interface specifications come from SIV project work or the partner programme, so the first step is getting them from SIV for your installation.

02 · Access

Each data domain may have its own path

The integrations SIV lists are partner-specific point solutions. Contracts, meter readings and payments may each sit behind a different interface, which the blueprint maps before any tool is built.

03 · Roadmap

The target is moving

SIV runs kVASy in parallel with a next-generation product for several years, with data synchronised between both. A connector built today has to know which of the two holds the record it reads.

04 · Data

Regulated billing and personal data

kVASy holds billing data and customer personal data. Every write path stays behind a person's confirmation, and reads follow the user's own kVASy rights.

Checked 21 September 2026

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

	What we found
Interfaces	kVASy web service interfaces (web services, type not published, docs not published): SIV names process-oriented web services, for example for mobile warehouse management and payment terminals, but publishes no protocol details or service catalogue · Partner interfaces (file/EDI, docs not published): the kVASy partner catalogue lists which point-to-point integrations exist, such as ELSTER or payment providers, not how they work · kVASy BI (database, docs not published): Oracle-based business intelligence layer; a possible read source, not documented as an API
Authentication	Not documented publicly. Check with SIV how the web services authenticate on your installation.
Vendor MCP server	No vendor server. No SIV or kVASy MCP server found, and no community server for kVASy.
Vendor AI assistant	SIV names AI as one of seven strategic priorities; the first live functions analyse incoming e-mails and WhatsApp requests automatically.
Other connectors	None found.

SIV.AG, part of Harris Computer Corporation (DE). German municipal utilities, regional suppliers, grid operators and water suppliers; SIV states more than 300 large and mid-sized companies as customers across the SIV group.

What we build

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

SIV.AG, part of Harris Computer Corporation does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# kvasy-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 details including end date
    backend: confirmed in blueprint
    mode: read
  get_meter_readings:      # meter or contract ID, date range -> readings with history
    backend: confirmed in blueprint
    mode: read
  list_invoices:           # customer ID -> invoices with amounts and status
    backend: confirmed in blueprint
    mode: read
  get_instalments:         # contract ID -> current instalment plan
    backend: confirmed in blueprint
    mode: read
  draft_instalment_change: # contract ID, new amount -> proposed instalment change for a person to confirm
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the kVASy 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.

kVASy 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 current instalment amount and the next invoice date for contract X?
Which meter readings are still missing for customer Y this billing period?
Show the last three invoices and the open payments for this customer.

What it will not do

Read more than the asking user may read in kVASy; permissions come from kVASy, not from the connector.
Change an instalment, invoice or contract by itself: the only write tool returns a proposal that a person confirms in kVASy.
Replace reporting: analysis across all contracts belongs in kVASy BI or a data warehouse, not in per-question calls.

When this is the wrong page

If the goal is sorting incoming customer e-mails and messages, SIV's own inbound management already does that inside kVASy. A connector is right when Claude, ChatGPT or Copilot has to answer from contract, meter and invoice data, or combine kVASy with another system.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your kVASy owners and checks every backend against your release and licence. Week two tests whether a person's own kVASy 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 kVASy 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: SIV: kVASy ERP suite · SIV: kVASy interfaces · SIV: kVASy integrations · SIV: apps and portals · SIV group · energie.blog interview (Feb 2026). 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 kVASy teams ask before the first tool call

Does kVASy have its own MCP server?

Not as of 21 September 2026. SIV names AI as a strategic priority, and its first live functions sort incoming e-mails and WhatsApp requests, but we found no MCP server from SIV or anyone else. An MCP server for kVASy has to be built against the interfaces SIV provides for your installation.

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

SIV does not publish its interface documentation, so this is a question for SIV. Check with SIV which web services your installation includes and whether they need a licence; the blueprint answers it before any tool is built.

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

No. The connector runs each call under the asking person's own kVASy 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 kVASy 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 kVASy administrator in the room if you like.