elster-mcp-server
Related Servers
Alternatives to elster-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to drive the German ELSTER tax portal by filling forms by Kennzahl, running checks, and reviewing exactly what would be sent, with final submission left to the user. It also supports read-only access to submissions, history, and inbox data plus draft and session management.3253 npm2MIT
- 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
- AlicenseAqualityAmaintenanceMCP server for the Canton of Bern tax portal TaxMe/BE-Login that reads account statements and tax returns via Playwright browser automation.138 npmMIT
- AlicenseBqualityCmaintenanceLocal-first MCP server that assists users with preparing and reviewing Italian tax declarations (Dichiarazioni) inside a controlled, user-authenticated Agenzia delle Entrate browser session, with a hard approval boundary preventing any external legal or financial action without explicit local approval.7Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLets MCP-speaking terminal agents read, click, type, fill forms, upload files and take screenshots in the user's own already-logged-in Chrome, so existing sessions stay signed in. Connects to the current browser via a Chrome extension instead of launching a fresh, empty one.MIT
- AlicenseBqualityDmaintenanceEnables AI-driven browser automation with advanced form testing, batch operations, and intelligent element extraction for MCP-compatible applications.149 npmMIT
TDQS
Scored across 29 tools
Most tools target distinct resources/actions (form editing vs. drafts vs. submissions vs. Belege vs. session handoff), and descriptions explicitly steer usage order. A few pairs overlap meaningfully: elster_submissions_list vs elster_sync_history (both read 'Übermittelte Formulare'), elster_submission_protocol vs elster_submission_archive (same protocol, one archives as PDF/HTML), and elster_form_check vs elster_form_review (review just adds the absenden overview). These are disambiguated in the text but still require careful reading.
All names are snake_case with an 'elster_' prefix, which is good, but the verb placement varies: noun_verb (elster_form_open, elster_drafts_list), verb-in-middle (elster_ustva_generate_xml, elster_form_handoff_wait), and bare noun_verb forms. Singular/plural is also inconsistent (elster_submissions_list vs elster_submission_protocol/archive; elster_belege_list vs elster_beleg_upload). Still readable, but not a predictable pattern throughout.
29 tools is heavy and above the comfortable 3–15 band. The domain is genuinely complex (login, config, UStVA, ESt form engine, drafts, submissions, Belege, handoff), so most tools earn their place, but the surface is large enough that an agent must navigate many near-sibling tools. Borderline: justified by scope but on the high side.
The ESt/form lifecycle is well covered end to end: open/new/page/set/add_row/delete_row/attach/crawl/check/review/handoff/wait/save, plus drafts, submissions, protocol, archive and Belege. However, several descriptions reference tools that do not exist in this set (elster_ustva_start, elster_eur_start, elster_est_start), leaving the UStVA submission path apparently incomplete and creating dead-end references. The document-upload and handoff flows round out coverage reasonably well.