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 にインストールします。
d.velop を Cloud にインストールClaude は AI のため誤ることがあります。回答をご確認ください。
2 分でセットアップ
- 1cloud.anythingmcp.com で無料トライアル開始。
- 2コネクターストアで d.velop documents をクリック。資格情報を貼り付け。
- 3MCP 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.
Search is HAL-shaped. Responses embed results under _embedded.repositories / _embedded.results and carry _links for paging. Follow _links.next.href rather than computing an offset; d.velop's cursors are not guaranteed to be stable integers.
Source ids narrow a search. A repository can expose several sources (index definitions); sourceid restricts a search to one of them, which is usually what makes a fuzzy search precise.
Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant — d.velop does not offer a public sandbox. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. 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.
あなたの AI は d.velop documents から 2 クリック先。
コネクターをインストール、資格情報を貼り付け、AI に質問。7 日間無料、クレジットカード不要。