Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

Related Servers

Alternatives to idoklad-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with the SuperFaktura invoicing system for managing invoices, clients, and expenses via natural language.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      19
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with the Polish National e-Invoice System (KSeF) for authentication, invoice creation, validation, and retrieval via 30 tools.
      32
      6
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides 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
      -

    TDQS

    A3.8/5.0

    Scored across 18 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues