sevdesk MCP server: connect AI agents to sevdesk from the EU

sevdesk is cloud accounting software from Offenburg, Germany, used by freelancers and small companies for invoices, receipts, bank reconciliation and VAT returns. sevdesk does not publish an MCP server of its own.

The open-source sevdesk-mcp project (joosthel/sevdesk-mcp on GitHub) fills the gap. It exposes 24 tools that together reach all 151 sevdesk API operations, adds audits that know what a wrong German booking looks like, and has been tested against a live account on bookkeeping system 2.0. It is MIT licensed and runs as a local stdio process.

Before the VAT return, an agent can run the VAT audit and the §13b report for the quarter and write a short note on what the Steuerberater should check, such as a US software supplier booked as domestic 0 % instead of reverse charge.

Other workflows: list bank payments without a receipt and ask the team for the missing documents, find suppliers whose monthly invoices stopped appearing, show who owes you money and for how long, or turn a chat message into a draft invoice for a customer.

Create an API token in sevdesk under Settings, Users, your user, API. On inference.eu, add the sevdesk connector to an agent and paste the token; it is stored encrypted in the EU and never shown again in full.

Set SEVDESK_READ_ONLY=true for the first weeks. A sevdesk token has no scopes and can do everything your login can, so read-only mode is the main control. When you are ready for writes, switch it off and consider SEVDESK_DRY_RUN to preview what each write would send.

The server talks directly to the sevdesk API at my.sevdesk.de, so your bookkeeping data goes to sevdesk, a German company, exactly as it does when you use the sevdesk app. No other service sits in between.

The agent then reads the results with a model that runs in EU data centres on inference.eu, and your API token is stored encrypted in the EU. Receipts and invoices contain personal data of customers and suppliers, so check that your sevdesk agreement covers this use.

The server is cautious by design. Read-only mode is enforced three times, invoices and vouchers are created as drafts, there is no email-send tool, and booked or paid vouchers cannot be rebooked through the API. Writes are never retried on an ambiguous failure, so a timeout cannot create a duplicate.

On inference.eu you can additionally require a person to approve each write call, such as creating an invoice or changing a tax rule, before the agent runs it. That keeps every booking decision with your bookkeeper.