Connector guide4-minute read6 MCP tools7 languages

Connect DATEV Sandbox to Claude via MCP

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

HCBy HelpCode teamUpdated 4 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

DATEV Online APIs (Sandbox)

DATEV Online APIs (Sandbox)

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

tools

6

Region

DE

Category

Accounting

Authentication

OAuth 2.0

Required env vars

DATEV_CLIENT_IDDATEV_CLIENT_SECRET
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

Guided setup

Connect DATEV Online APIs to Claude in 2 minutes

Start a free trial on AnythingMCP Cloud, connect DATEV Online APIs in the guided setup, then add your MCP URL to Claude. No code and no server to run.

No credit card · 7-day trial · Self-host alternative available

AnythingMCP is listed in Claude's connector directory: add it to Claude in one click (opens in a new tab), then sign in and choose which MCP servers Claude may use.

Try asking

Example prompts for DATEV Online APIs (Sandbox)

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

DATEV Online APIs (Sandbox) · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → DATEV Online APIs (Sandbox), paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

DATEV Online APIs (Sandbox) + Claude

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

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:

DATEV_CLIENT_ID, DATEV_CLIENT_SECRET

Step 1 — Get credentials

Setting up takes about 10 minutes. You need an app on the DATEV-Entwicklerportal and a DATEV-Konto to sign in with.

  1. On the DATEV-Entwicklerportal (https://developer.datev.de), create a Confidential app with OpenID Connect Authorization Code Flow. Set the redirect URI to <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
  2. Subscribe the app to the sandbox API products accounting:clients 2.0 and accounting:documents 2.0.
  3. Copy the client ID into DATEV_CLIENT_ID and the client secret into DATEV_CLIENT_SECRET. Copy the secret in full: the portal shows it only once.
  4. Install the connector. It is already set up for DATEV's sandbox endpoints and authenticates at the token endpoint with HTTP Basic (client_secret_basic), which DATEV requires.
  5. On the connector page, click Authorize with Provider and log in with your DATEV-Konto. This is a one-time sign-in: the refresh token is then stored encrypted.
  6. Run datev_list_clients: it lists the Mandanten your DATEV-Konto user is provisioned for, with UUID, consultant number, client number and name.

Sandbox, not production: every DATEV app runs in the sandbox until DATEV completes its production-approval review, so this is where you build and test. The sandbox works against DATEV's test data. Once DATEV approves your app for production, use the separate DATEV Online APIs connector: it takes the same credentials and points at the production endpoints.

Scopes: the connector asks for datev:accounting:clients accounting:clients:read accounting:documents. Do not add openid: it is the issuer name, not a scope.

Two kinds of client id: every per-client tool takes a clientId, the Mandant UUID that datev_list_clients returns. It is not the same as DATEV_CLIENT_ID, which identifies your OAuth app and is sent in the X-DATEV-Client-Id header on every call, together with the Bearer token.

What it reads: a Mandant's master data (consultant and client number, name, address); the Mandanten with DATEV Unternehmen online (DUO) document access, which can be fewer than all of them because only clients with an active DUO subscription appear; a Mandant's document types (Belegtypen); and the DUO version with the file extensions DUO accepts for upload. All six tools only read.

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 Claude

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 shows YOUR_SERVER_ID.

Recommended path — works on claude.ai web without editing any config file.

  1. In Claude, open Customize → Connectors.
  2. Click +, then Add custom connector.
  3. Enter a name, e.g. DATEV Online APIs (Sandbox), and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
  4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

All tools below appear in your chat — start typing prompts.

Available tools

ToolWhat it does
datev_list_clientsList DATEV accounting Mandanten (clients) your DATEV-Konto user is provisioned for, from the accounting-clients v2 master-data product
datev_get_clientGet one Mandant's master data (consultant/client number, name, address) from accounting-clients v2
datev_documents_list_clientsList the subset of Mandanten that have DATEV Unternehmen online (DUO) document access via the accounting-documents v2 product
datev_get_documents_clientGet one Mandant's basic data as exposed by the accounting-documents v2 product (the DUO view, distinct from the accounting-clients master…
datev_list_document_typesList the document types (Belegtypen) configured for a Mandant on DATEV Unternehmen online — needed before uploading documents so you know…
datev_get_duo_versionGet the DATEV Unternehmen online (DUO) version and the permitted file extensions for document upload on a given Mandant

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes — point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Next steps

Was this guide helpful?

Connect DATEV Online APIs to Claude in 2 minutes

Start a free trial on AnythingMCP Cloud, connect DATEV Online APIs in the guided setup, then add your MCP URL to Claude. No code and no server to run.

Related guides

Connectors

Connect DATEV Sandbox to ChatGPT via MCP

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

Connectors

Connect DATEV Sandbox to Microsoft Copilot via MCP

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

Connectors

Connect DATEV Sandbox to Cursor via MCP

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

Connectors

Connect DATEV Sandbox to Gemini CLI via MCP

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

Connectors

Connect DATEV Sandbox to Meta Muse via MCP

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.

Connectors

DATEV Sandbox MCP Server: Clients and Document Types

Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.