sevDesk MCP Server

What is an MCP server for sevdesk?

An MCP server for sevdesk connects AI agents to your sevdesk instance via the open Model Context Protocol. The AI agent then gets standardised access to the sevdesk REST API — it can create invoices, evaluate receipts, retrieve open items, prepare payment reminders or pull reports from the booked data, always within clearly defined tools and permissions.

sevdesk has established itself as cloud accounting for self-employed people and small mid-sized businesses — as an alternative to Lexoffice (somewhat lighter), DATEV (considerably simpler) and Excel (obviously). With the DATEV export offered by sevdesk, the tax advisor always stays on board. Accounting data is particularly sensitive: customer names, revenue, margins, bank details. That is exactly why MCP is so valuable here: the agent does not get full access to all data, but only the fields and operations the respective use case really needs.

The sevdesk REST API (token-based) is publicly documented. Important in advance: according to sevdesk, the API is only available from the Buchhaltung Pro plan. This is of interest above all for self-employed people, agencies and consultancies with a small team who want to move accounting from typing in data to approving it.

Use cases: what can a sevdesk MCP server do in concrete terms?

1. Automatic receipt recognition & posting An incoming receipt (PDF, JPG, photo). The agent recognises supplier, date, amount and VAT rate and proposes the account assignment. For recurring suppliers it learns patterns — the effort falls every week. Accounting only has to confirm.
2. DATEV export workflow by voice "Prepare the DATEV export for April" — the agent checks open receipts, identifies missing account assignments, writes reminders to the responsible people, then generates the export from sevdesk and places it in the tax advisor's folder.
3. Dunning automation The agent runs through the open-items list from sevdesk every day, recognises overdue invoices, proposes a dunning level and wording (friendly → firm → final deadline), and reminders go out after confirmation. The sevdesk status is updated automatically.
4. Cash flow reports by voice "What does the cash flow look like next week?" The agent pulls receivables, payables and standing orders from sevdesk, adds planned incoming payments and delivers a concrete answer — ideal before larger investment decisions.
5. Invoice preparation from project data From project management or time tracking, the agent pulls the billable services, checks them against the contract and creates an invoice draft in sevdesk. Employees review and send.
6. Tax advisor communication Is the tax advisor asking for a receipt or a clarification? The agent searches sevdesk, finds the posting, checks attachments and answers the question with a link to the receipt — the back-and-forth by email shrinks dramatically.

How the integration works

Architecture:

AI agent ↔ MCP server (EU host) ↔ sevdesk REST API (token-based, JSON)

Concrete steps:

• API access & token: The prerequisite is the Buchhaltung Pro plan. According to the API documentation, every sevdesk administrator has their own API token, which is valid indefinitely and works with the rights of this account. We therefore set finer permissions per use case in the MCP server itself: only the approved tools, only the necessary fields.
• Tool definitions: Typical tools: list_invoices, get_open_items, create_voucher, book_voucher, send_reminder, get_datev_export. Each with a JSON schema.
• Data minimisation: Even within the token rights we filter out fields — bank details, internal margin fields or confidential customer names become visible only where the use case really needs them.
• Write operations & approval: Receipts are usually created as a proposal and approved by accounting or the tax advisor. Invoices are always sent under the four-eyes principle.
• Detecting events: Optionally, the MCP server checks at fixed intervals for new receipts, incoming payments or overdue invoices and then triggers the appropriate process.

sevdesk vs. Lexoffice MCP — a short comparison

Both tools are excellent for SME accounting, both have good APIs, both are MCP-capable. The short rule of thumb:

• sevdesk: Stronger for self-employed people, freelancers and agencies with project-based billing. The UI is somewhat more playful, onboarding is low-threshold.
• Lexoffice: Stronger for classic SME accounting, trading businesses and multi-stage accounting. Closer DATEV integration, historically grown.
• MCP architecture: Almost identical. The use cases (receipts, dunning, cash flow, DATEV export) can be implemented on both tools in exactly the same way.

For more depth: MCP server for Lexoffice or MCP server for DATEV.

GDPR, hosting & security

Accounting data is subject to special requirements — GoBD (German bookkeeping rules), retention obligations, data protection. Our standard for sevdesk MCP:

• EU hosting for the MCP server (Germany or the Frankfurt region).
• Limited rights in the MCP server: The sevdesk token itself carries administrator rights, so it is stored encrypted on the server and the agent only gets fixed, defined tools per use case.
• Data minimisation: Margin fields, bank details and contract details hidden by default.
• DPA with the AI provider, EU data residency (Claude via AWS Bedrock EU, Azure OpenAI in an EU region, etc.).
• Logging: Every tool call documented — timestamp, affected receipt/invoice, person triggering it. That keeps every change traceable.
• Tax advisor integration: The DATEV export stays unchanged. The tax advisor only notices that the receipts "finally arrive on time".

What does it cost?

• Use-case-oriented approach: First get receipt recognition or dunning into production — then expand.
• First results with one clearly defined use case are realistic.

Frequently asked questions

Which sevdesk API does the MCP server use?

The official sevdesk REST API with token authentication. According to sevdesk, the API is included from the Buchhaltung Pro plan. Every sevdesk administrator has the API token; it is valid indefinitely and carries the rights of this account, so we set narrow permissions in the MCP server through fixed, defined tools. It covers receipts, invoices, contacts, categories, postings and DATEV export.

Can the AI agent post receipts automatically?

Yes. In practice we work with a proposal-and-approval pattern: OCR/recognition, account assignment proposal, approval by accounting or the tax advisor. Direct posting without approval is possible but typically not recommended.

Does the DATEV export keep working as usual?

Yes, the sevdesk DATEV export stays unchanged. The MCP server only helps prepare the month-end close — tracking down missing account assignments, matching receipts, answering the tax advisor's questions.

sevdesk vs. Lexoffice — which tool for MCP?

Both have good APIs and are MCP-capable. sevdesk is strong for self-employed people and service providers, Lexoffice for classic SME accounting. The MCP architecture is almost identical — the choice depends on the tool you already use.

Is this GDPR- and GoBD-compliant?

Yes, if the chain is right: MCP server in the EU, tools with firmly limited rights, field filtering, a DPA with the AI provider with EU data residency and a complete log of every access. The GoBD obligations themselves continue to be met by sevdesk; the agent creates receipts as a proposal and posting happens after approval.

Can the agent react to new receipts?

Yes. Optionally, the MCP server checks at fixed intervals for new receipts, incoming payments or status changes and then prepares the next step, such as a dunning proposal.

Which AI models are supported?

All MCP-compatible ones: Anthropic Claude, OpenAI GPT, Google Gemini, Microsoft Copilot.