For utilities running Schleupen.CS
A Schleupen MCP server gives Claude, ChatGPT or Copilot named tools for business partners, SLP energy quantities, changed market locations and ledger postings. Schleupen.CS offers SOAP web services and REST APIs documented on its Developer Campus behind a login. Schleupen ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
Why Schleupen.CS is hard for agents
01 · Docs
The Integration track on Schleupen's Developer Campus needs an account, so the service descriptions are not openly readable. The public GitHub samples show how a call works, not which services your installation has.
02 · Protocol
The core business services are SOAP with WSDL, not one REST API. Each call needs a session token from its own service and Windows authentication or OpenID Connect, so the connector has to manage tokens per user.
03 · Versions
The general ledger interface and the EDM master data export are Schleupen.CS 3.0 interfaces. On an older installation those tools are not available, so the tool list depends on your release.
04 · Market
Market messages run through AS4 with certificates and EDIFACT formats. An agent should read their status at most and never send a market message.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | Schleupen.CS web services (SOAP, docs behind customer or partner login): WSDL-based services such as PersonEntityService v3.0 with Query, Validate and SaveChanges, plus a separate session token service; public .NET samples on GitHub, the service catalogue needs a Developer Campus login · Privileged web APIs (REST/JSON, docs behind customer or partner login): general ledger interface (OpenAPI), SLP energy quantity API, master data export for EDM and a CRM connector API in preview; several of them exist only for Schleupen.CS 3.0 · AS4 Connect API (REST/JSON, docs behind customer or partner login): cloud-managed AS4 market communication; an open-source adapter on GitHub handles EDIFACT and schedule files, client certificates are issued by Schleupen |
| Authentication | Web services accept Windows authentication or OpenID Connect, with a session token from CreateSessionTokenActivityService. The AS4 Connect API uses client certificates issued by Schleupen SE. |
| Vendor MCP server | No vendor server. No Schleupen MCP server found; Schleupen's AI work is a KI-Hub for connecting language models, the MAIA documentation assistant and a web assistant in the CS.IT portal. |
| Vendor AI assistant | MAIA answers documentation questions on an open-source model, the CS.IT customer portal has a web assistant, and a KI-Hub connecting OpenAI, Gemini, Mistral, Perplexity or local models was announced on 27 January 2026. |
| Other connectors | None found. |
Schleupen SE (DE). German municipal utilities and water suppliers in the roles of supplier, grid operator and metering point operator; Schleupen states that every fourth German Stadtwerk works with Schleupen.CS.
What we build
Built on what Schleupen SE documents: persons (business partners), SLP market locations and energy quantities, new and changed market and metering locations, general ledger postings, CRM-relevant customer data, AS4 market communication messages. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# schleupen-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_business_partner: # name or ID -> person master data
backend: PersonEntityService v3.0 Query
mode: read
get_slp_energy_quantity: # market location, period, market role -> computed SLP energy quantity
backend: SLP energy quantity API
mode: read
list_changed_locations: # since date -> new and changed market and metering locations
backend: master data export (EDM) interface, CS 3.0
mode: read
get_gl_postings: # period -> general ledger postings handed to the ledger system
backend: general ledger interface (OpenAPI), CS 3.0
mode: read
draft_partner_update: # business partner, proposed change -> validated change for a person to confirm
backend: PersonEntityService v3.0 Validate, then SaveChanges after confirmation
mode: propose
audit: every call logged with user, tool, arguments and the Schleupen.CS responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Schleupen.CS 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.
When this is the wrong page
If the question is about Schleupen.CS documentation, MAIA answers it inside Schleupen's own tools. If your team wants a model inside Schleupen's processes, ask Schleupen about the KI-Hub first; a connector is right when Claude, ChatGPT or Copilot has to read live Schleupen.CS data or combine it with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Schleupen.CS owners and checks every backend against your release and licence. Week two tests whether a person's own Schleupen.CS 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 Schleupen.CS 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.
Not as of 21 September 2026. Schleupen has the MAIA documentation assistant, a web assistant in the CS.IT portal and a KI-Hub for connecting language models, announced in January 2026. An MCP server for assistants outside Schleupen has to be built against the Schleupen.CS web services and APIs.
The interface descriptions sit in the Integration track of Schleupen's Developer Campus, which needs an account, and several of the APIs are privileged. Check with Schleupen which services and licences your contract covers; the blueprint confirms this before any tool is built.
No. Each call runs under the asking person's own Windows or OpenID Connect sign-in with a session token, so Schleupen.CS decides every answer. Two users asking the same question can get two different answers, and that is tested before go-live.
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
Thirty minutes with the engineer who would build the connector, with your Schleupen.CS administrator in the room if you like.