idoklad-mcp
Related Servers
Alternatives to idoklad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with the SuperFaktura invoicing system for managing invoices, clients, and expenses via natural language.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage Slovak invoicing through Doklado's public APIs, including listing and retrieving invoices, downloading PDFs, emailing invoices, and issuing or updating them. It also supports sending, receiving, and acknowledging Peppol eFaktúra documents via SAPI+.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to read orders, stock, prices, contractors, payments, debts, and sales from SmartUp ERP, with optional write capabilities for creating and updating orders and contractors when explicitly enabled.19MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with the Polish National e-Invoice System (KSeF) for authentication, invoice creation, validation, and retrieval via 30 tools.326MIT
- FlicenseNot gradedqualityCmaintenanceProvides read-only access to inv.bg invoicing data, enabling users to list clients and invoices and retrieve full document details and line items through natural language in Claude.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to issue Italian FatturaPA electronic invoices and transmit them to the SdI via Invoicetronic. Supports creating and querying invoices with Italian VAT rates.MIT
TDQS
Scored across 18 tools
Each document type has a clear list/get pair (received invoices, issued invoices, proforma, credit notes) and the contacts/price list/codebook tools target distinct resources. The only mild overlap is among the analytics trio (get_business_stats, get_top_partners, get_contact_stats), but their descriptions carve out separate report scopes, and search_api_docs vs idoklad_api_request are explicitly sequenced as a discovery/call pair.
The dominant pattern is consistent verb_noun snake_case (list_*, get_*), applied across most of the surface. Minor deviations are get_document_pdf (noun object rather than a resource) and idoklad_api_request (namespaced noun), but both remain readable and predictable.
18 tools is slightly above the ideal band but justified: four document families each need a list and get, plus contacts, price list, PDF export, stats, codebook, and a generic API escape hatch. No tool appears redundant, though the four parallel list/get pairs make the surface feel heavier than strictly necessary.
The read-only domain (invoices, contacts, price list, statistics, codebooks, PDF export) is well covered, and the search_api_docs + idoklad_api_request pair provides an escape hatch for bank statements, cash vouchers, stock and other endpoints. Minor gaps: no get_price_list_item detail tool, and no issued/received document creation or update (consistent with the stated read-only design).