sevDesk
sevDesk cloud bookkeeping for German SMBs and freelancers: contacts, invoices, vouchers (Belege), orders, parts and bank accounts. REST API v1, API-key auth — the key goes in a bare Authorization header, with no Bearer prefix.
7 天免费 · 无需信用卡 · EU 托管
问 sevDesk 任何事
通过 AnythingMCP 对 sevDesk 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 sevDeskClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 sevDesk。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 sevDesk
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Getting a key
- Sign in to sevDesk and open Einstellungen → Benutzer → (your user) → API-Token.
- Copy the token into
SEVDESK_API_KEY. It belongs to one user in one client (Mandant) and inherits that user's permissions — create a dedicated API user with read rights if the agent should not be able to write.
The Authorization header has no scheme. sevDesk expects the raw token (Authorization: abc123…), not Bearer abc123…. This adapter sends it that way; if you build a custom connector against sevDesk by hand, that is the single most common reason for a 401.
Object names are capitalised and singular: the collection is /Contact, /Invoice, /Voucher, /Order, /Part — not /contacts. Responses wrap the rows in {"objects": [...]}.
Embedded objects: most rows reference other objects only by {id, objectName}. Pass a comma-separated embed (e.g. embed=contact,contactPerson) to have sevDesk expand them inline rather than making the agent fetch each one.
API version: v1 at https://my.sevdesk.de/api/v1. sevDesk has published a v2 preview; v1 remains the supported production surface.
Writes: sevdesk_create_contact creates a real contact. Invoice creation is deliberately not exposed — sevDesk requires a multi-step create-position-then-book flow whose partial failure leaves an unusable draft, so an invoice is better created in the UI.
Cloud reachability: my.sevdesk.de is public with a valid certificate; AnythingMCP Cloud reaches it directly.