datev-extf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_datev_extfA | Check a DATEV-Format (EXTF) CSV file, e.g. EXTF_Buchungsstapel.csv or a Debitoren/Kreditoren export, before importing it into DATEV or after DATEV rejected it. Returns every problem with line, field and a plain-language explanation in German or English: dot instead of comma in amounts, missing leading zeros in Belegdatum, BU-Schlüssel on automatic accounts, account length, encoding, header errors and more. Pass a file path (preferred, the encoding is checked too) or the file content. |
| explain_datev_findingA | Explain what a validate_datev_extf finding code (e.g. amount-dot, bu-automatic, date-leading-zero) means and how to fix it. Placeholders like {value} or {max} stand for values from the specific finding. |
| write_buchungsstapelA | Create a DATEV-Format Buchungsstapel (EXTF, Formatversion 13) from booking rows, ready for import into DATEV Rechnungswesen or DATEV Unternehmen online. The result is checked with the validator before it's returned. With outputPath the file is written as Windows-1252, the encoding DATEV expects; without it the CSV text is returned. The tool formats bookings, it doesn't choose accounts or tax keys: take those from the user or their tax advisor. |
| list_datev_columnsA | List the columns (line 2) of a DATEV Buchungsstapel (Formatversion 13, 125 columns) or Debitoren/Kreditoren file (254 columns), numbered by position. Use it to map export fields to DATEV columns or to find a column named in a finding. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fix_datev_import | Validate a DATEV EXTF file and propose fixes for what DATEV would reject. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| buchungsstapel-columns | |
| debkred-columns | |
| findings-de | |
| findings-en |
TDQS
Scored across 4 tools
Each tool has a single, distinct responsibility: listing columns, validating files, explaining validation findings, and writing a Buchungsstapel. The only close pair is validate/explain, but one performs checks while the other only resolves finding codes, so there is no real ambiguity.
All tools follow a consistent snake_case verb_noun pattern: list_datev_columns, validate_datev_extf, explain_datev_finding, write_buchungsstapel. The verbs are clear, consistently placed first, and there is no mixing of naming conventions.
Four tools is well-scoped for this focused DATEV EXTF helper server. Each tool covers a distinct part of the workflow and none feels redundant or unnecessary.
The Buchungsstapel lifecycle is well covered: list columns, validate, explain errors, and write a pre-validated file. However, list_datev_columns and validate_datev_extf also cover Debitoren/Kreditoren files, but there is no corresponding writer for that format, leaving a noticeable gap.