Skip to main content
Glama
Sign In
tezga-mcp

tezga-mcp

by GoSimple-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to tezga-mcp

No user-submitted related servers found.

    Related Servers

    • gofact

      kOlapsis
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes French electronic invoicing as a local stdio MCP server, letting an AI client create EN 16931-compliant Factur-X invoices with guaranteed legal numbering, client and organization management, and invoice history. It can also submit a generated invoice to a French e-invoicing platform (PDP) after explicit confirmation.
      5
      AGPL 3.0

    • BlockMag Public MCP Server

      AddrianC
      A
      license
      A
      quality
      C
      maintenance
      Provides zero-authentication access to six free AI tools for discovering verified storefronts, searching live product catalogs by name or EAN-13 barcode, generating printable A4 VAT invoices and timesheet PDFs, and verifying invoice QR codes. Runs as a remote SSE/HTTP endpoint or a local Node.js stdio bridge for Claude Desktop, Cursor, and other MCP clients.
      6
      MIT
    • BillingEngine MCP server

      BillingEngine MCP serverofficial

      billingengine
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients such as Claude and Cursor to manage customers, create and update draft invoices, list or download invoices as PDF and XML e-invoices, and record and list payments in a BillingEngine account. It runs locally with your API key and never deletes data.
      10
      335 npm
      MIT

    • WorkPulse MCP Server

      aliasdhacker
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Claude to enter and query expenses, invoices, and contracts in a WorkPulse instance via its REST API, with 14 tools, batch rollback, and stdio or OAuth-protected Streamable HTTP transports while keeping credentials server-side.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool maps to a distinct step in the fiscalization lifecycle (environment check, issue, storno/refund, advance, single-document status, document listing). The only mild overlap is between tezga_stanje_dokumenta (one document by ID) and tezga_lista_dokumenata (filtered listing), and between tezga_izdaj_racun and tezga_avans, but the descriptions make the boundaries clear. The combined storno/refund tool bundles two actions, though its vrsta parameter disambiguates them.

    Naming Consistency3/5

    All names share a consistent tezga_ snake_case prefix, which aids grouping. However, the stems mix verb phrases (izdaj_racun) with bare noun phrases (okruzenje, avans, stanje_dokumenta, lista_dokumenata), and one name is a compound with 'ili' (storno_ili_refundacija), so the pattern is readable but not uniform.

    Tool Count5/5

    Six tools is well-scoped for an invoicing/fiscalization server: one per major operation plus a listing and a status lookup. No tool feels redundant or like padding.

    Completeness4/5

    The surface covers the full core lifecycle: environment check, invoice issuance, storno/refund, advance invoices, status retrieval and document listing, with idempotency and production confirmation handled. Minor gaps exist — no direct document lookup by externalId or a dedicated PDF/QR retrieval tool (links are only returned at issue time).

    Resources