Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the d.velop documents in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
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.
Try asking
Example prompts for d.velop documents
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → d.velop documents, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
d.velop documents + Gemini
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.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
DVELOP_URL, DVELOP_API_KEY
Step 1 — Get credentials
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.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Gemini
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Gemini CLI reads MCP servers from ~/.gemini/settings.json (or %APPDATA%\gemini\settings.json on Windows). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Get your MCP API key from AnythingMCP → MCP Servers → your server → API keys.
- Save the file and restart
gemini. - Run
/mcpinside the Gemini CLI —d.velop documentsshould be listed as available. - Vertex AI Studio: pass
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_IDto thetoolsarray of your request with the sameX-API-Keyheader.
Available tools
| Tool | What it does |
|---|---|
d_velop_list_repositories | List the repositories in this d |
d_velop_get_repository | Read one repository's definition: its name, the sources (index definitions) it exposes and the operations it supports |
d_velop_search_documents | Search a repository by full text and/or property filter |
d_velop_get_document | Read one document's metadata: its display name, category, creation and modification dates, version and property values |
d_velop_get_document_versions | Read the version history of one document — who changed it, when, and with what comment |
d_velop_list_categories | List the document categories (Dokumentarten) defined in a repository with their display names and property sets, so a search can filter by t |
FAQ
Does Gemini 1.5 Pro or 2.x support MCP? Yes — Gemini CLI ≥ 0.4 and Vertex AI tools API both accept MCP httpUrl connectors with custom headers.
Next steps
Was this guide helpful?