Integration

Klardaten integration

Klardaten connects an on-premise DATEV installation (the German tax and accounting software) to the cloud through its connector and gateway. Read DATEV master data (clients, addressees, their communications and relationships), DMS document records and filing standards, the status of corporate, trade, income tax and VAT returns, available tax calculations, accounting data (clients, fiscal years, postings, monthly sums and balances), the tax firm's own analytics (clients, staff, orders, fees, expenses, sub-orders, invoices, capacity), search indexed DMS documents (add-on), manage data-change and instance-status webhooks, and read instance health, usage and metrics. These data routes belong to the Klardaten Enterprise API reference. Not exposed: account, user, organization and billing administration, instance setup and restarts, profile and credential management, payroll (HR LODAS) data, extended client records with bank and personal tax identifiers, bank transactions, tax return contents and calculated tax values, connector-local datasets, logs and audit-log downloads, and the raw DATEVconnect proxy. Birth dates, gender, personal tax identification numbers and open custom fields are withheld from client, addressee and staff records. Webhook signing secrets are returned only in the vendor's raw answers, which this integration does not pass on, so deliveries cannot be signature-checked (the vendor calls verification optional). Authentication is a Klardaten user API key (uk-...) sent as a Bearer token, plus the client instance id of your DATEV system (x-client-instance-id) and an optional DATEVconnect profile id (x-profile-id).

Connect Klardaten How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Klardaten.Built from the 49 Klardaten tools below, on the connection you add once.

What you can do with Klardaten

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Data change webhook, 3 operations

create_data_change_webhookCreate data change webhookPOSTAgents: ask firstSubscribes an HTTPS endpoint to insert, update and delete events of one DATEV entity in the instance. Klardaten POSTs each change; failed deliveries are retried up to 10 times (5 s timeout each).
delete_data_change_webhookDelete data change webhookDELETEAgents: ask firstDeletes a data-change webhook; change events stop being delivered to its endpoint.
list_data_change_webhooksList data change webhooksGETAgents: ask firstLists your data-change webhooks: id, destination endpoint, tracked entity, instance and creation date. Their signing secrets are not returned here.

Monitoring webhook, 3 operations

create_monitoring_webhookCreate monitoring webhookPOSTAgents: ask firstSubscribes an HTTPS endpoint to status changes of one client instance (it goes up or down). Failed deliveries are retried up to 10 times with exponential backoff.
delete_monitoring_webhookDelete monitoring webhookDELETEAgents: ask firstDeletes a monitoring webhook; instance status notifications stop being delivered to its endpoint.
list_monitoring_webhooksList monitoring webhooksGETAgents: ask firstLists your monitoring webhooks (notified when an instance goes up or down): id, endpoint, instance and creation date. Signing secrets are not returned here.

Addressee, 2 operations

get_addresseeGet addresseeGETAgents: ask firstReturns one DATEV master-data addressee (person or company) by id: name, type, status, roles, contact details, business tax numbers, VAT id and company data. Personal data.
list_addresseesList addresseesGETAgents: ask firstLists DATEV master-data addressees (persons and companies), paged: name, type, status, roles, contact details, business tax numbers, VAT id and company data. Personal data.

Client, 2 operations

get_clientGet clientGETAgents: ask firstReturns one DATEV client (Mandant) from master data by client id: number, name, type, status, contact details, tax office numbers, company form, industry, client group and compliance checks. Business and personal data.
list_clientsList clientsGETAgents: ask firstLists the DATEV clients (Mandanten) of the instance from master data, paged (page, page_size): number, name, type, status, contact details, tax office numbers, company form, industry and client groups. Business and personal data.

Client instance, 2 operations

get_client_instanceGet client instanceGETAgents: ask firstReturns one Klardaten client instance (a connected DATEV system): name, consultant number, owner, connection type, service status, last reply, connector version and DATEVconnect service user.
list_client_instancesList client instancesGETAgents: ask firstLists your organization's Klardaten client instances (connected DATEV systems): id (the Client Instance ID), name, consultant number, connection type, status, connector version, last reply and whether it is a test instance.

Corporate tax return, 2 operations

get_corporate_tax_returnGet corporate tax returnGETAgents: ask firstReturns the status record of one corporate income tax return by id: year, client, status, ELSTER transmission and notice dates (not the return's content).
list_corporate_tax_returnsList corporate tax returnsGETAgents: ask firstLists corporate income tax (Koerperschaftsteuer) returns in DATEV, paged: year, client and consultant number, status, ELSTER transmission status and dates, tax office notices (status metadata, not the return's content).

Document, 2 operations

list_documentsList documentsGETAgents: ask firstLists DATEV document management (DMS) document records, paged and filterable: id and number, folder, register, year, month, description, keywords, correspondence partner, booking and e-invoice status (metadata only, no file content).
search_documentsSearch documentsPOSTAgents: ask firstSearches indexed DATEV DMS documents with a German or English query and returns ranked documents with snippets and metadata. Needs Klardaten's local document search add-on. Reads only.

Income tax return, 2 operations

get_income_tax_returnGet income tax returnGETAgents: ask firstReturns the status record of one income tax return by id: year, client, status, ELSTER transmission and notice dates (not the return's content).
list_income_tax_returnsList income tax returnsGETAgents: ask firstLists income tax (Einkommensteuer) returns in DATEV, paged: year, client and consultant number, status, ELSTER transmission status and dates (status metadata, not the return's content).

Relationship, 2 operations

get_relationshipGet relationshipGETAgents: ask firstReturns one master-data relationship by id: type, source and target addressee, validity dates and shareholding data.
list_relationshipsList relationshipsGETAgents: ask firstLists master-data relationships between addressees across the instance, paged: type, source and target addressee, validity dates and shareholding data (shares, capital, profit share).

Trade tax return, 2 operations

get_trade_tax_returnGet trade tax returnGETAgents: ask firstReturns the status record of one trade tax return by id: year, client, status, ELSTER transmission and notice dates (not the return's content).
list_trade_tax_returnsList trade tax returnsGETAgents: ask firstLists trade tax (Gewerbesteuer) returns in DATEV, paged: year, client and consultant number, status, ELSTER transmission status and dates (status metadata, not the return's content).

Vat return, 2 operations

get_vat_returnGet vat returnGETAgents: ask firstReturns the status record of one VAT return by id: year, client, status, ELSTER transmission and notice dates (not the return's content).
list_vat_returnsList vat returnsGETAgents: ask firstLists VAT (Umsatzsteuer) returns in DATEV, paged: year, client and consultant number, status, ELSTER transmission status and dates (status metadata, not the return's content).

Accounting client, 1 operation

list_accounting_clientsList accounting clientsGETAgents: ask firstLists the clients that have DATEV accounting (Rechnungswesen) data in the instance, paged.

Addressee communication, 1 operation

list_addressee_communicationsList addressee communicationsGETAgents: ask firstLists one addressee's communication entries (phone numbers, email addresses and similar) with type, content and whether each is the main one. Personal data.

Client instance service, 1 operation

list_instance_required_servicesList instance required servicesGETAgents: ask firstLists the DATEV service areas this client instance is set up to require (accounting, master-data, dms, iam, order-management, hr and others).

Client relationship, 1 operation

list_client_relationshipsList client relationshipsGETAgents: ask firstLists one client's master-data relationships to other addressees (managing directors, shareholders, spouses and so on): type, name, target addressee and validity dates.

Client service, 1 operation

list_client_servicesList client servicesGETAgents: ask firstLists the DATEV services (programs, with category and year) available for one client.

Datevconnect health, 1 operation

get_datev_connect_healthGet datev connect healthGETAgents: ask firstReturns the latest 100 DATEVconnect service-status changes of an instance in the selected period (monitoring data is kept 14 days): timestamp and each service's health status.

Document metadata, 1 operation

search_document_metadataSearch document metadataPOSTAgents: ask firstLists stored DATEV DMS file records by dates, structured filters and optional filename or keyword matching, newest filings first, paged with a cursor. Needs the document search add-on. Reads only.

Employee capacity, 1 operation

list_employee_monthly_capacityList employee monthly capacityGETAgents: ask firstLists monthly capacity planning per firm employee (tax-advisory analytics), paged: total, planned, overtime and non-plannable capacity, executed and client work time.

Filing standard, 1 operation

list_filing_standardsList filing standardsGETAgents: ask firstLists the DATEV filing standards (Ablage-Knigge): document classes with their standard folder and register.

Firm client, 1 operation

list_firm_clientsList firm clientsGETAgents: ask firstLists the tax firm's clients (tax-advisory analytics), paged: number, name, type, start and end dates, branch, company, subject area, responsible persons, industry, legal form and payment terms.

Firm employee, 1 operation

list_firm_employeesList firm employeesGETAgents: ask firstLists the tax firm's staff (tax-advisory analytics), paged: number, name, short code, group, branch, company, employment dates, occupation, qualification, partner and cost center. Personal data.

Firm invoice, 1 operation

list_firm_invoicesList firm invoicesGETAgents: ask firstLists the tax firm's outgoing invoices (tax-advisory analytics), paged: invoice number, year and date, order, company, branch, billing person, net, VAT and gross amounts.

Fiscal year, 1 operation

list_fiscal_yearsList fiscal yearsGETAgents: ask firstLists the accounting fiscal years of one client.

Instance metrics, 1 operation

get_instance_metricsGet instance metricsGETAgents: ask firstReturns resource metrics of an instance's host over a period: CPU and memory of the machine and connector process, database CPU, memory and I/O, and queued and processing request counts.

Instance usage, 1 operation

get_instance_usage_statsGet instance usage statsGETAgents: ask firstReturns HTTP request statistics of an instance in minute bins (granularity_minutes, default 10): status class, request count and average response time.

Order, 1 operation

list_ordersList ordersGETAgents: ask firstLists the tax firm's orders (Auftraege) (tax-advisory analytics), paged: order number and description, assessment and fiscal year, company, branch, subject area, cost center, client and responsible persons.

Order category, 1 operation

list_client_order_categoriesList client order categoriesGETAgents: ask firstLists, for one client number, each order category with its latest fully invoiced year: orders, responsible persons, revenue, costs and contribution margins.

Order expense, 1 operation

list_order_expensesList order expensesGETAgents: ask firstLists recorded efforts and expenses per order and sub-order (tax-advisory analytics), paged: billing months, effort type, employee, work date, time units and amounts.

Order fee, 1 operation

list_order_feesList order feesGETAgents: ask firstLists billed fee items per order and sub-order (tax-advisory analytics), paged: fee plan and number, invoice text, legal basis (paragraph and section), units, rates and item values.

Order value, 1 operation

list_order_valuesList order valuesGETAgents: ask firstLists financial totals per order (tax-advisory analytics), paged: fees, expenses, advances, on-account and credit amounts and outstanding fees.

Partial order, 1 operation

list_partial_ordersList partial ordersGETAgents: ask firstLists sub-orders (Teilauftraege) (tax-advisory analytics), paged: billing months, work start and end, calculation and invoicing dates, revenue, costs, advances and payments.

Posting, 1 operation

list_postingsList postingsGETAgents: ask firstLists accounting postings (Buchungen), paged: date, fiscal year, account and contra account, description, amounts, tax rate, currency, document fields and cost centers. Filter by fiscal year and client, as the vendor advises.

Processing status, 1 operation

list_processing_statusesList processing statusesGETAgents: ask firstLists the processing status entries of orders and sub-orders (tax-advisory analytics), paged: planned and actual dates and employees, processing topic, status and remarks.

Tax calculation, 1 operation

list_tax_calculationsList tax calculationsGETAgents: ask firstLists the DATEV tax calculations available for one client in one tax application (income-tax, corp-tax, trade-tax or vat-return): id, tax year and label.

Trial balance, 1 operation

get_monthly_trial_balanceGet monthly trial balanceGETAgents: ask firstReturns one client's sums and balances list (Summen- und Saldenliste) for a year, cumulated up to the given month: per account the debit and credit totals, current-month movements, balance and transaction counts.

Use Klardaten from Claude Code, Cursor or Codex

Connect Klardaten in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Klardaten operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Klardaten

Create your workspace
Sign up free. Nothing to install.
Connect Klardaten once
Add your Klardaten connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.