sevdesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEVDESK_API_TOKEN | Yes | Your sevdesk API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_contactsC | List all contacts from sevdesk. Supports filtering by various parameters. |
| get_contactB | Get a specific contact by ID from sevdesk |
| create_contactC | Create a new contact in sevdesk |
| update_contactC | Update an existing contact in sevdesk |
| delete_contactB | Delete a contact from sevdesk |
| list_invoicesC | List all invoices from sevdesk. Supports filtering and pagination. |
| get_invoiceB | Get a specific invoice by ID from sevdesk |
| get_invoice_pdfC | Get the PDF of an invoice as base64 encoded string |
| send_invoice_by_emailC | Send an invoice via email |
| mark_invoice_as_sentC | Mark an invoice as sent |
| book_invoiceB | Book an invoice (mark it as paid) |
| cancel_invoiceB | Cancel an invoice (creates a cancellation invoice) |
| list_vouchersC | List all vouchers (receipts/expenses) from sevdesk |
| get_voucherA | Get a specific voucher by ID from sevdesk |
| book_voucherC | Book a voucher (mark it as paid) |
| get_voucher_positionsB | Get all positions (line items) of a voucher |
| upload_voucher_fileC | Upload a file (receipt image/PDF) for a voucher |
| list_check_accountsB | List all check accounts (bank accounts) from sevdesk |
| get_check_accountB | Get a specific check account by ID |
| get_check_account_balanceC | Get the current balance of a check account |
| list_transactionsC | List all transactions of a check account |
| get_transactionB | Get a specific transaction by ID |
| create_transactionC | Create a new transaction in a check account |
| list_partsC | List all parts (products/services) from sevdesk inventory |
| get_partB | Get a specific part by ID |
| create_partC | Create a new part (product/service) in sevdesk |
| update_partB | Update an existing part in sevdesk |
| get_part_stockB | Get the current stock of a part |
| list_tagsC | List all tags from sevdesk |
| get_tagA | Get a specific tag by ID |
| create_tagB | Create a new tag and attach it to a document (Invoice, Voucher, Order, or CreditNote) |
| update_tagA | Update an existing tag's name |
| delete_tagB | Delete a tag from sevdesk |
| list_tag_relationsA | List all tag relations (shows which documents have which tags) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
Each tool targets a distinct resource-action pair (e.g., create_tag vs. list_tags, send_invoice_by_email vs. mark_invoice_as_sent). Even with 34 tools, there is no ambiguity; every tool has a unique purpose and domain.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_tag, get_invoice, list_transactions). Prepositional phrases are used uniformly (e.g., send_invoice_by_email, get_check_account_balance), and there is no mixing of conventions.
34 tools is on the higher end but appropriate for a comprehensive accounting server covering tags, invoices, vouchers, contacts, check accounts, transactions, and parts. Each tool serves a specific function; no tool appears redundant.
Significant gaps exist: missing create_invoice, update_invoice, create_voucher, update_voucher, and update/delete for check accounts and transactions. Core CRUD operations for invoices and vouchers are absent, which will hinder common workflows.