Architecture & data flow
How a tool call travels from SovrGPT through GovBridge into the DMS and back to the AI model: building blocks, data flow and every step of a call.
GovBridge consists of two separate building blocks that share the SovrGPT database and one encryption key.
| Building block | Location | Task |
|---|---|---|
| Provisioning | SovrGPT platform (/admin/govbridge) | Creates endpoints per organisation: generates a slug and bearer token, stores the backend URL and the encrypted credentials. |
| Adapter service | govbridge.sovrgpt.com (Netherlands, europe-west4) | Accepts MCP calls, resolves the tenant, calls the backend live and translates between MCP and CMIS or FIT-Connect Submission API v2. |
The adapter knows no SovrGPT sessions, users or chat histories. It only sees the slug, the token and the single tool call with its arguments.
Data flow at a glance
┌─────────────┐ MCP (JSON-RPC) ┌───────────────┐ CMIS (JSON/HTTP) ┌─────────────┐
│ SovrGPT │ ───────────────▶ │ GovBridge │ ─────────────────▶ │ DMS │
│ (Frankfurt) │ ◀─────────────── │ (Netherlands) │ ◀───────────────── │ (your org) │
└─────────────┘ tool result └───────────────┘ API response └─────────────┘
│ ▲
│ │ ↓ chat with tool result
▼ │ ↑ next tool call or answer
┌─────────────┐
│ AI model │
│ (as chosen) │
└─────────────┘SovrGPT sends the tool call to the adapter, the adapter fetches the data from the DMS, and SovrGPT passes the result to the AI model chosen in the chat. Location and provider of each station: Security & privacy. With FIT-Connect, the backend is FITKO's submission API; the payload leaves the adapter end-to-end encrypted (JWE).
One tool call, step by step
- SovrGPT sends
POST https://govbridge.sovrgpt.com/<slug>/<protocol>withAuthorization: Bearer <bridge-token>and a JSON-RPC 2.0 body. - Routing: exactly two path segments,
POSTonly;<protocol>must be inGOVBRIDGE_PROTOCOLS(e.g.cmis,fit-connect). - Tenant: two-factor tenant resolution;
failure → generic
401. - Body limit: hard 1 MB limit (single call or batch).
- Dispatch:
initialize,tools/list,tools/call,ping; fortools/callthe plugin for the protocol. - Call the backend live via
fetchwith a hard timeout. The CMIS plugin reads or files documents and applies the size policy; the FIT-Connect plugin encrypts (JWE) and runs throughannounce → attachments → finalize. - Response: the adapter logs metadata only and sends the JSON-RPC response back
(
202for pure notifications). - SovrGPT passes the result to the AI model, which answers or calls the next tool.
Statelessness
Every request carries its own tenant context; there are no per-connection sessions. Process RAM holds only the backend OAuth token per endpoint (until shortly before it expires) and the CMIS repository service document (5 minutes). The adapter never caches business content.