elster-mcp-server
Related Servers
Alternatives to elster-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to fill any German ELSTER tax form by Kennzahl, start or continue returns, run the portal's own checks, and review every row before transmission. It never submits; the finished form is handed off in a visible browser for the user to send.29MIT
- AlicenseNot gradedqualityBmaintenanceA local Windows automation MCP server that lets a KI-Agent safely control the SteuerSparErklärung tax software: inventory and open tax cases, read pages, compare receipts and values, and edit verified working copies, with all ELSTER transmission paths locked tight.MIT
- AlicenseAqualityBmaintenanceMCP server for the Canton of Bern tax portal TaxMe/BE-Login that reads account statements and tax returns via Playwright browser automation.1311 npmMIT
- FlicenseNot gradedqualityCmaintenanceLets Claude validate German tax data offline — tax IDs, IBANs, tax numbers, tax offices, certificate expiry, and full return XML with optional preview PDF — then submit returns to ELSTER through the official ERiC library running on your own machine. Submissions are test-only by default, with live filing gated behind an operator flag and explicit per-return approval.-
- AlicenseAqualityDmaintenanceAn MCP server that allows AI assistants like Claude to automate interactions with the German tax portal ELSTER via Puppeteer, including form filling, submission, and session management.1451 npm34MIT

invowerkofficial
AlicenseNot gradedqualityBmaintenanceEnables creating ZUGFeRD PDFs and XRechnung invoices and validating ZUGFeRD/Factur-X, XRechnung (KoSIT), and Peppol BIS e-invoices through an MCP endpoint, returning validation reports.MIT
TDQS
Scored across 32 tools
Most tools target clearly distinct actions (form_set vs form_add_row vs form_delete_row, ustva_start vs est_start vs eur_start), but several have overlapping read purposes: elster_sync_history and elster_submissions_list both read the same 'Übermittelte Formulare' area, elster_form_check is a subset of elster_form_review, and elster_form_crawl overlaps elster_form_page. Descriptions are detailed enough to mitigate most misselection, but the duplication is real.
Names consistently use snake_case with an elster_ prefix and a domain segment (form_, ustva_, session_, sync_), making the pattern predictable. Minor deviations: singular vs plural of the same noun (beleg_upload / belege_list, submission_protocol / submissions_list).
32 tools is on the heavy side even for a genuinely complex domain spanning ESt/EÜR/UStVA forms, browser sessions, receipts, drafts, and sync. Several tools look consolidatable (session_list vs session_status, submissions_list vs sync_history, check vs review), pushing it past a comfortably scoped surface.
Coverage is broad: login/config checks, form lifecycle (open/new/page/set/add/delete/save/check/review), UStVA-specific helpers, receipts list/upload, eDaten fetch, drafts, and submission history/protocol. Gaps are minor and partly by design (submission deliberately limited to UStVA; no receipt deletion/update, no explicit logout).