SuperFaktura MCP by usefulapi

Each tool has a clearly distinct resource and action; singular get_* versus plural list_* pairs are well differentiated, and create/add operations target different entities (client, contact person, invoice, expense, tag). Descriptions reinforce boundaries, such as draft-only invoice creation versus expense recording, so misselection is unlikely.

All tool names follow the same superfaktura_ prefix plus snake_case verb_noun pattern. The verbs used are consistent and predictable (add, create, get, list), with meaningful singular/plural distinctions between get and list tools.

At 25 tools the set is on the heavy side of the 16-25 borderline range, even for a broad accounting ERP. Many read-only reference/list endpoints could potentially be consolidated, though each does cover a distinct SuperFaktura resource.

Coverage is read- and create-heavy: clients, invoices, expenses, tags, and stock have create/get/list operations, but there are no update, delete, send, mark-paid, or payment-recording tools. Common accounting workflows such as editing a client, deleting a draft, sending an invoice, or recording a payment reach dead ends.