Connecting your own systems and line-of-business applications

Connect a DMS, ERP or line-of-business system to SovrGPT through an MCP bridge that translates REST, SOAP or CMIS, without a proprietary connector.

You connect existing software such as a DMS, ERP, line-of-business application or internal tool to SovrGPT through an MCP bridge. SovrGPT talks to external systems only through the Model Context Protocol (MCP), while most systems speak REST, SOAP or CMIS. The bridge translates between the two.

What is an MCP bridge?

Lean middleware with two sides: towards SovrGPT it speaks MCP (JSON-RPC over Streamable HTTP), towards your software it speaks that software's existing interface, such as REST, OData, SOAP, CMIS or GraphQL. A new system needs a new bridge; SovrGPT itself does not change.

The bridge decides which endpoints and fields the model can see at all. Usually you or your integration partner run it yourselves. SovrGPT then only knows its address and a token, and your software's credentials stay with you. For public authorities there is also GovBridge, a bridge operated by rooom AG.

Architecture at a glance

┌──────────┐   MCP (JSON-RPC)    ┌──────────────┐   REST/SOAP/CMIS   ┌────────────────┐
│ SovrGPT  │ ──────────────────▶ │  MCP bridge  │ ─────────────────▶ │ Legacy software│
│  (EU)    │ ◀────────────────── │ (your infra) │ ◀───────────────── │ (DMS/ERP/LOB)  │
└──────────┘   tool result       └──────────────┘   API response     └────────────────┘

In the chat, the model calls a tool, for example "search for a case file".
SovrGPT sends the call to the bridge, which translates it for your software.
The response comes back as a tool result.
The model selected in the chat writes the answer from it. Where it runs is listed under Models.

Three ways to provide a bridge

Variant	Who operates the bridge?	When does it make sense?
A: the vendor ships MCP	Your software vendor	with modern SaaS tools (see Marketplace)
B: your own bridge	You or your partner, in front of the existing interface	software with an open API but without MCP
C: generic adapter	A standard bridge for an open standard such as CMIS, for example GovBridge	several systems sharing the same standard

Connecting it in practice

Run the bridge in your infrastructure (container or VM), reachable over HTTPS.
In SovrGPT, go to Marketplace → "Eigenen MCP-Server hinzufügen" (add your own MCP server) and enter a name, the bridge URL and a header with the token, for example Authorization: Bearer ….
The tools are then available in the chat through the MCP button.

At the start of every answer, SovrGPT connects to all selected servers at the same time. If a server does not return its tool list within 10 seconds, the chat answers without that server's tools. The other servers are not affected.

The header is stored encrypted with AES-256-GCM per organisation and is never visible in the browser. For your own servers, SovrGPT does not ask before write actions. So only expose write tools if the model may use them without asking.

Public-sector line-of-business applications

For public authorities, the marketplace has two templates for open eGovernment standards:

Template	Standard	Purpose
VIS / DMS case file	CMIS (OASIS)	Search and read case files and documents in a public-sector DMS (VIS suite, nscale, Fabasoft …)
FIT-Connect	FIT-Connect (FITKO)	Deliver OZG applications to line-of-business systems in a standardised way

In each you enter the address of your bridge (your own or GovBridge) and the token. SovrGPT asks in the chat before every write action. One bridge covers several DMS products because CMIS and FIT-Connect are open standards. Connections inside a specific line-of-business application remain a separate project.

A platform admin enables the templates per organisation (entitlement Behörden-Konnektoren, public-sector connectors); other organisations do not see them.

Security

Tokens are stored encrypted per organisation on the server. Every tool call is stored with its name, status, duration and a shortened preview of input and result (up to 1,800 characters). Recognisable passwords, keys and tokens are redacted in that preview. Only the person who created a chat can see its calls; the marketplace shows the recent ones under "Letzte MCP-Aufrufe" (recent MCP calls).

SovrGPT does not call addresses in internal networks: localhost, private and link-local address ranges, and internal names such as .internal or .local. This is checked before every request, including after name resolution. SovrGPT does not follow redirects. Enter the final, publicly reachable address of the bridge.

More on the protocol and editor clients: MCP server · ready-made connections: Marketplace.