d.velop documents
d.velop documents (d.3one) DMS: search the repository, read document metadata and source properties, list repositories and categories. REST API on d.velop cloud or on-premises, bearer API key.
7 天免费 · 无需信用卡 · EU 托管
问 d.velop 任何事
通过 AnythingMCP 对 d.velop documents 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 d.velopClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 d.velop documents。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 d.velop documents
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Getting an API key
- In d.velop cloud open Konfiguration → API-Schlüssel (or, on premises, the identityprovider app) and create an API key for a technical user.
- Give that user read rights on the repositories the agent should reach. d.velop applies its permission model per document, so a restricted user quietly sees a smaller repository.
- Set
DVELOP_URLto your tenant root —https://<tenant>.d-velop.cloudfor cloud, or your own host on premises — andDVELOP_API_KEYto the key.
The Authorization header is Bearer <apikey>, with the API key used directly as the bearer token. d.velop's API keys are long-lived; rotate them the way you would rotate a password.
Repository ids come first. d.velop can host several repositories in one tenant and every document operation is scoped to one. Call d_velop_list_repositories and keep the id — it is an opaque string, not a number.
Responses are HAL JSON. d_velop_list_repositories returns repositories[] (id, name); a search returns items[], each with id, sourceProperties and sourceCategories, plus _links.next.href for the next page. page starts at 1 and pageSize defaults to 25.
Every search and document read needs a source id. d.velop maps its internal properties to a source, and the search (/srm) and document (/o2m) endpoints return property values only through that mapping: sourceid is required. Call d_velop_list_categories first: it returns the repository's default source with its id (normally /dms/r/<repositoryId>/source), its category keys and its property keys. Use that id as sourceid, the category keys in sourcecategories and the property keys in sourceproperties.
Not run against a live tenant. The paths and parameters follow d.velop's DMSApp OpenAPI specification (help.d-velop.de/dev/documentation/dms-app); d.velop does not offer a public sandbox. If you run this against a real system, a correction to the adapter JSON is genuinely welcome.
Read-only by design: no upload, no property change. A DMS is the audit trail, and an agent should not be able to edit it by accident.