Skip to main content
Glama
olegtyshcneko

KSeF MCP

by olegtyshcneko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to KSeF MCP

No user-submitted related servers found.

    Related Servers

    • mcp-ksef-pl

      cmendezs
      A
      license
      A
      quality
      B
      maintenance
      Model Context Protocol (MCP) server for Polish Electronic Invoicing (KSeF / FA(2)). Provides tools to validate, generate, and explore API specifications for KSeF interoperability.
      10
      181 PyPI
      3
      Apache 2.0

    • mcp-facturacion-electronica-es

      cmendezs
      A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Spanish Electronic Invoicing. Provides tools to generate, validate, and submit invoices across VERI\*FACTU, Facturae/FACe, SII, TicketBAI, and Crea y Crece B2B.
      20
      2
      Apache 2.0

    • einvoice-mcp

      makririch
      A
      license
      A
      quality
      D
      maintenance
      MCP server for DACH e-invoicing. Create XRechnung (UBL) and ZUGFeRD 2.3 (Factur-X CII) invoices, validate against EN 16931 rules, extract data from XML, and convert between UBL, CII and JSON formats.
      6
      30 npm
      2
      MIT

    • @invapi/mcp-server

      invapi-org
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Invapi E-Invoicing API, enabling conversion, validation, and extraction of invoices in UBL, CII, ZUGFeRD, Excel, and more.
      26 npm
      MIT

    • ksef-mcp

      Dev10x-Guru
      A
      license
      A
      quality
      A
      maintenance
      Enables running a local MCP server for Poland's KSeF (Krajowy System e-Faktur) e-invoicing system, so invoice data stays on the user's own machine rather than passing through an intermediary service. It currently exposes only a diagnostic server_info tool, with invoice search and retrieval tools still to come.
      6
      1
      AGPL 3.0
    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

    B3.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear workflow phases (drafting, validation, submission, retrieval). Minor overlap exists among source-document/provenance tools and between exchange-rate lookup/advice, but descriptions generally clarify boundaries.

    Naming Consistency4/5

    All tools share a ksef_ prefix and mostly follow verb_noun conventions (validate_nip, list_invoices, submit_invoice). A few names deviate, like ksef_session_status (missing verb) and ksef_test_connection_check (awkward phrasing), but the pattern remains predictable.

    Tool Count3/5

    23 tools fall in the heavy range for a single server, though the KSeF domain spans source documents, drafting, validation, and submission. The count is justifiable but leans high, with several advisory/provenance utilities that could potentially be consolidated.

    Completeness4/5

    The server covers a full invoice lifecycle: source ingestion, drafting, validation, XML preparation, submission, and retrieval/UPO download. Minor gaps exist (no source-document update/delete, no explicit draft retrieval/cancel), but agents can complete core workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources