Use d.velop documents with AI via MCP
d.velop documents manages files and records from intake to audit-proof archiving in many public authorities, savings banks and mid-sized companies. The vendor does not offer an MCP server, but it does offer a well-structured set of REST APIs on which we build the CompanyGPT integration.
What is d.velop documents?
d.velop documents is the ECM and document management system of d.velop AG, based in Gescher, Germany. It covers audit-proof archiving, digital case files, incoming mail processing and document workflows, and runs both as a cloud service and on-premises. d.velop positions itself as a fully European provider and offers the d.velop agent center as its own AI process hub.
The value for AI applications lies in the file structure: documents are assigned to cases, customers or employees and enriched with metadata. An assistant can therefore go beyond full-text search and answer in context – for example which documents are still missing from a case file, or how a case has developed over time.
Connection at a Glance
- MCP server
- None available – individual integration via REST
- Interfaces
- DMS App API, Document Reader API, User Management API, d.velop sign API
- Authentication
- d.velop identity provider (API key / bearer token)
- Operating model
- Hybrid – cloud or on-premises
- Permissions
- Access per repository and file type, role-based control in CompanyGPT
How to Connect d.velop documents to CompanyGPT
d.velop AG does not provide an MCP server for documents. We therefore build the CompanyGPT connection as an individual integration on the official REST interfaces.
The most relevant ones are the DMS App API for search, upload and download, the Document Reader API for content analysis, and the User Management API for permission mapping; the d.velop sign API is added for signature processes. Authentication runs through the d.velop identity provider using an API key or bearer token. From the required operations we generate an OpenAPI description and expose it to CompanyGPT as MCP tools – scoped to the repositories and file types intended for the use case.
Whether you run d.velop documents as a cloud service or in your own data centre does not change the functional interface, only the route to it: with a cloud instance CompanyGPT calls the API directly, with an on-premises installation it goes through your network setup. In both cases your administrators define by role and group which teams work with the integration.
Note for on-premises operation: CompanyGPT runs in your own Azure tenant – so your on-premises network can be connected directly: via a site-to-site VPN (Azure VPN Gateway) or ExpressRoute between your corporate network and the virtual network of your CompanyGPT environment. The system does not need to be publicly reachable; we set up the connection together with your IT team.
Typical Use Cases
How AI agents in CompanyGPT work with d.velop documents
Get into a case file quickly
Case handlers and specialist departments have the contents of a large file summarized before they start working on it.
Check completeness
The agent compares a case file against the documents the process expects and flags what is missing – for example in application or onboarding procedures.
Stay ready to respond
When customers or citizens follow up, the assistant finds the relevant documents via metadata and full text and points to their location in the archive.
Frequently Asked Questions
d.velop documents and AI – the most important answers
Is there an MCP server for d.velop documents?
No, d.velop AG does not offer an MCP server for documents. We establish the connection to CompanyGPT through the system's official REST APIs.
Which APIs do you use for the integration?
Usually the DMS App API for search and document access, the Document Reader API for content, and the User Management API. We describe the required calls as an OpenAPI specification and expose them as MCP tools.
How are permissions taken into account?
The integration only gets access to the agreed repositories and file types. In addition, role and group controls in CompanyGPT determine which employees may invoke the integration at all.
Does the integration differ between cloud and on-premises?
Functionally no – the same REST APIs are available in both operating models. What differs is how your CompanyGPT environment reaches the system; an installation in your own data centre adds the network link.
What does this mean for data protection?
CompanyGPT runs in your own cloud tenant and calls the d.velop APIs directly, without intermediaries. Processing inside d.velop documents itself is unchanged and remains governed by your existing contract with the vendor.
d.velop documents and Your AI – GDPR-Compliant with CompanyGPT
CompanyGPT is the enterprise AI assistant in your own cloud tenant: all relevant AI models, your company data and integrations like d.velop documents – centrally managed, with roles and permissions. We set up the connection together with you.
d.velop documents is a trademark of its respective owner (d.velop AG). Its mention describes compatibility and does not imply any partnership or endorsement. Availability and scope of the connection depend on the respective vendor.