GovBridge — connecting line-of-business systems
SovrGPT's hosted MCP adapter for public-sector DMS and line-of-business systems — CMIS and FIT-Connect in real time, strictly EU-hosted, without proprietary connectors.
GovBridge is the multi-tenant MCP adapter operated by eNetworkers that connects SovrGPT to classic public-sector and line-of-business backends. It translates between the Model Context Protocol that SovrGPT speaks and the open eGovernment standards that legacy software offers. GovBridge supports two protocols:
- CMIS 1.1 (Content Management Interoperability Services, an OASIS standard) — for read and write access to case files and documents in public-sector DMS.
- FIT-Connect (Submission API v2) — for OZG-compliant, end-to-end encrypted delivery of applications to public-sector destinations.
GovBridge is the fully operated form of the bridge concept described in Connecting your own systems — you do not have to develop or host an adapter yourself.
What is GovBridge for?
Public-sector DMS such as VIS suite, nscale, Fabasoft, Alfresco or OpenText publish their case files and documents over CMIS. GovBridge makes exactly those holdings usable in the SovrGPT chat: a case worker asks for a file in plain language, and the model searches, reads and (on request) writes directly in the DMS — without anyone ever having to build a proprietary connector. Through FIT-Connect the same model can additionally submit finished applications securely to a destination.
| Question in the chat | What GovBridge does |
|---|---|
| "Find the building file for Müllerstraße 12." | CMIS folder search → result list with objectIds |
| "Show me the latest building application in it." | CMIS document search → metadata + content |
| "Summarise the PDF." | Fetch content (size policy) → the model summarises |
| "File the minutes in the case file." | createDocument (only when writing is enabled) |
| "Submit the application to destination X." | FIT-Connect: E2E-encrypted announce → attachments → finalize (only when writing is enabled) |
What sets GovBridge apart
- Real time, no caching. Every tool call pulls the data live from the DMS API endpoint provided by the customer. GovBridge does not cache any business content.
- Strictly EU-hosted. The service runs exclusively in EU data centres
(Amsterdam,
europe-west4), reachable atgovbridge.sovrgpt.com. No hyperscaler in the data path. - Multi-tenant & isolated. Every organisation gets its own endpoint (slug + token). A two-factor resolution (URL slug and bearer token) binds every call unambiguously to exactly one tenant.
- Least privilege. The model can only call a tightly scoped set of curated
tools (
cmis_*,fit_*) — no raw CMIS SQL pass-through and no arbitrary FIT-Connect API access. Write actions can be switched off per endpoint and additionally require confirmation (confirm_writes). - Metadata-only logging. Only metadata is logged (org/endpoint IDs, tool, duration, status) — never content, tokens or credentials.
The chapters
- Architecture & request flow — how a tool call travels from SovrGPT through the bridge into the DMS and back.
- Tools & interfaces — the
cmis_*andfit_*tools, their parameters, the CMIS browser binding and the FIT-Connect Submission API v2. - Setup — provision an endpoint, store backend credentials, connect it in SovrGPT.
- Security & compliance — encryption, auth modes, GDPR, audit.
- Operations — hosting, configuration, size limits, error behaviour.
Availability
GovBridge is a public-sector feature: a platform admin unlocks it per
organisation through the entitlement public-sector connectors. Corporate tenants
do not see it by default. For the generic bridge architecture and other ways of
providing one, see Connecting your own systems.
Connecting your own systems and line-of-business applications
Attach legacy software with a REST/SOAP/CMIS API to SovrGPT through a lean MCP bridge — no proprietary connectors.
Architecture & request flow
How an MCP tool call travels from SovrGPT through GovBridge into the line-of-business system and back — the two building blocks, the two-factor resolution and the complete path of a call.