Skip to main content
Glama
SignalEDI

SignalEDI MCP Server

Official
by SignalEDI

Related Servers

Alternatives to SignalEDI MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Let AI agents read, validate and acknowledge EDI documents. Parses raw X12 and EDIFACT interchanges into structured JSON, validates envelope integrity, produces plain-language summaries, and generates 997 Functional Acknowledgments.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to parse, validate, summarize, and convert X12 EDI documents (such as 850 purchase orders and 810 invoices) into structured JSON through callable MCP tools.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to locally parse, validate, audit, explain, generate, and convert XRechnung and ZUGFeRD/Factur-X e-invoices using official rule sets, fully offline with no API keys required.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query and manage QuickBooks Online data through natural language, including customers, invoices, bills, vendors, accounts, and financial reports.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      InvoiceXML brings e-invoice compliance to your AI agent. Create, validate, convert, render, and extract structured invoices across UBL (Peppol BIS Billing 3.0, used worldwide), CII, Factur-X, ZUGFeRD, and XRechnung, all checked against the EN 16931 standard and official Schematron rules. Ask your assistant to generate a compliant invoice, validate one for errors, or convert between formats, with n
      5
      MIT

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation2/5

    lookup_x12 and lookup_element_definition are explicitly the same operation under different names, creating direct overlap. search_docs and lookup_x12 also share a search-like purpose, though descriptions differentiate them. Other tools are clearly distinct.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (search_, get_, lookup_, generate_, explain_). No mixed conventions or irregular prefixes exist.

    Tool Count5/5

    With 7 tools, the server is well within the ideal 3-15 range for its EDI reference scope. The one redundant alias tool is a minor blemish but does not make the set bloated or thin.

    Completeness4/5

    The tool surface covers the main workflows for an EDI documentation/sandbox server: searching docs, retrieving schemas, looking up X12 definitions, generating examples, explaining errors, and producing test documents. Minor gaps exist (e.g., no explicit supported-transaction-set listing), but no critical dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues