DATEV Sandbox MCP Server: Clients and Document Types

💡 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)

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.

Setup

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.

Prerequisites: DATEV_CLIENT_ID, DATEV_CLIENT_SECRET

Install the connector locally

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

Open http://localhost:3000/connectors/store, pick DATEV Online APIs (Sandbox) and paste in the env vars listed under Prerequisites.

Available tools

Next steps

• Connect to Claude
• Connect to ChatGPT