d.velop documents and AI: is there an MCP server?

d.velop documents is the document management system of d.velop AG in Gescher, Germany. Anyone who wants an AI assistant such as Claude or ChatGPT to work with these documents asks first: is there an MCP server for it?

In short

Yes, according to d.velop. d.velop AG lists its own MCP interface on its pricing page. It belongs to the Business and Ultimate plans and needs an activated d.velop pilot. We found no public guide with a server address. The functional description names neither an address nor setup steps. A free connector from a third party also exists, see below.

What d.velop offers itself

The MCP interface. According to the functional description (version of 21 October 2026, in German), it exposes functions and content of d.velop products over the Model Context Protocol. It is a third access channel next to the user interface and the REST API. The description names tools, resources and prompts. As tool examples it names the search for documents and files, including content-based matches, and questions about documents. The pricing page lists three tools: d.velop pilot Assistant Search, d.velop pilot Document Prompt and d.velop agents. d.velop decides which functions are available. We found no complete tool list.

Plans. The pricing page lists “access via Model Context Protocol (MCP)” as included in Business and Ultimate and not in Basic. This holds in the tables for AWS, T Cloud Public and Hybrid. We did not find the row in the On-Premises table.

Requirements. According to the functional description, you need an MCP client with OAuth 2.1 or bearer token, a d.velop documents environment with the MCP interface activated, and an activated, configured d.velop pilot. The user needs the right permissions in d.velop documents.

Sign-in and permissions. According to the functional description, access is bound to one signed-in user. Technical service users are not planned. The AI agent can reach only data and functions that the user may use. The functional description does not say whether the server can also write or delete.

Claude, ChatGPT, Copilot. On the pages we read, d.velop names no specific assistant. On its Intelligent Document Processing page, d.velop writes that MCP lets you integrate the d.velop content platform into other AI ecosystems. We found no guide or approval from d.velop for Claude, ChatGPT or Copilot. The pilot page names ChatGPT and Copilot only as a contrast to d.velop AI.

REST APIs. The developer portal lists many APIs, including the DMS app for documents and metadata, the identity provider, webhooks and an Open API for the d.velop pilot. There is also a Power Automate connector that uses an API key.

AI in the product. According to d.velop, the d.velop pilot needs an existing d.velop documents repository and answers questions about your own documents. According to the pricing page, d.velop bills the pilot by usage through d.velop AI credits. Since 28 September 2026, according to d.velop, it can also run agents with skills. According to d.velop, the agents are currently available only to AWS and Azure customers, and they need a confirmed supplemental agreement. d.velop does not say whether this also applies to the MCP tool “d.velop agents”. According to d.velop, use through MCP also consumes d.velop AI credits. According to its product page, the d.velop agent center is in development and not yet for sale. The facts page calls it “currently available in beta”.

Data location. According to d.velop, the cloud runs on AWS and T Cloud Public (formerly Open Telekom Cloud). Depending on configuration, processing and storage in the German and/or European legal area is possible. For AI features, d.velop sends inputs and documents encrypted to the AI provider in use. According to d.velop, its AI partners do not train on them. According to the pilot page, d.velop supplies models by use case by default, including providers outside Europe. The same page advertises “European data storage as the default”. According to d.velop, you can choose a purely European setup. The data processing agreement names the provider. We found no page that fixes the data location for every customer.

What the community offers

We found no MCP server from d.velop on GitHub. The d-velop account holds SDKs, app templates and an n8n connector. A free MCP server from a third party exists: the open-source gateway AnythingMCP (AGPL-3.0). It includes a d.velop connector with six tools, all read-only according to its catalogue page. The connector uses the REST API with the API key of a technical user and does not run at d.velop. According to the README, the self-hosted Community edition is free for up to 3 active users. According to the connector definition, its authors did not test it against a live d.velop tenant. AnythingMCP also offers a hosted cloud with a 7-day trial, according to its guide. innfactory builds a connection on the REST APIs and writes that d.velop offers no MCP server. That contradicts d.velop’s pricing page. We follow d.velop. We found no d.velop offer on Zapier or viaSocket. Make blocks automated requests, so we did not check there.

What this means for your company

• Check whether your plan includes MCP. According to the pricing page, Basic does not.
• The d.velop pilot must be activated and configured. Ask about costs through AI credits.
• The assistant sees only what the signed-in user may see. Check permissions in d.velop documents.
• Before you start, ask d.velop which AI provider is used and where it processes data. The data processing agreement names it.
• What reaches the AI assistant falls under its terms, not d.velop’s.