What was built
An MCP server wrapping the DATEV Connect API, so the accounting data a German firm keeps in DATEV is reachable from an AI assistant instead of only from the DATEV client. Reads are the primary use; writes go where the API allows them, and only with the firm named in the confirmation.
| Area | Description |
|---|---|
| Endpoint inventory | The DATEV API documentation turned into a capability matrix and a prioritised tool list, rather than wrapping endpoints at random |
| Client & master data | The pull tools the firm actually needs first, validated against a real DATEVconnect environment |
| Multi-tenancy | Fail-closed firm resolution and firm-named write confirmations, so a tool call can never touch the wrong firm's books |
| On-prem agent | A polling agent with an allowlisted command executor for the DATEVconnect installations that never leave the firm's network |
| Cloud deployment | Azure Container Apps with Bicep infrastructure, Entra ID app registrations, test users and role groups in a dedicated sandbox tenant |
| CI/CD | Containerised builds where a docs-only commit does not rebuild the image, and a red test job does not silently ship |
| Compliance | AVV under Art. 28 and the professional-secrecy commitment under §203 StGB handled from day one, not retrofitted |
Dr. Schauer is the pilot firm. The design target is a connector that a second and third firm can be onboarded onto without rebuilding it.
Tech stack
| Technology | Role |
|---|---|
| DATEV | The accounting system being wrapped, via DATEVconnect and the cloud API |
| Pipedrive | The CRM side the same assistant reaches through MetaPipe |
Project stats: 67 tasks, ~23h, running since May 2026.
Recently touched
- 2026-09-06 M8 — Schauer pilot rollout & compliance Open
- 2026-09-06 Auth & connection handling (DATEVconnect / cloud) In Progress
- 2026-09-05 Schauer tenant onboarding: ComputerBauer credentials into vault + first deploy attempt Open
- 2026-09-04 M5 — On-prem relay agent (.NET 8, MSI, signed) Open
- 2026-09-04 Windows CI: build + sign + MSI smoke matrix Open
Other projects in this case study
Kanzlei MCP
A team-facing MCP layer so the firm's staff move CRM and operational data through Claude instead of clicking through the Pipedrive interface. Only supervisors work in the CRM UI; everyone else gets…
Read case studyWhat we built
- Tool surface
- Inbound sync
- Alerting
- Meeting notes
- Deployment
- Onboarding
CRM
The client-acquisition process of a German tax and advisory firm, rebuilt in Pipedrive. The Neumandatsprozess starts with a qualification form and ends with an onboarded client, and every step in…
Read case studyWhat we built
- Qualification form
- Classification routing
- Pipedrive structure
- Reception path
- Telephony
- Inbound sync