Edi Bridge Mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.2Updated Oct 24, 2026

EDI X12 / EDIFACT B2B bridge — parse, validate, map, govern (Peppol/ViDA).

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant parse, validate, map and govern EDI X12 and EDIFACT B2B supply-chain messages, including Peppol and ViDA checks.

What you can do
  • Parse EDI X12 and EDIFACT business messages into structured form
  • Validate EDI messages against their rules
  • Map EDI messages to a modern representation
  • Apply governance checks such as Peppol, ViDA and SOX
When to use it
Useful when you work with B2B supply-chain documents in X12 or EDIFACT and want an assistant to inspect, check or convert them, or to run Peppol/ViDA governance checks on them.
Requirements
Runs as a local process over stdio, installed from the PyPI package edi-bridge-mcp and started with Python. No authentication, environment variables or headers are declared.
Before you install
The README describes bridging messages to a separate OS, so consider where parsed business documents end up. No credentials or write actions are documented; review the code before sending real trading-partner data.

Installation

In SourceWeft

  1. Open Edi Bridge Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

edi-bridge-mcp

mcp-name: io.github.CSOAI-ORG/edi-bridge-mcp

Part of the CSOAI Layer-0 legacy-bridge family. Bridge EDI X12 / EDIFACT B2B supply-chain messages to ONE OS — parse, validate, map, govern (Peppol/ViDA/SOX).

Tools: parse_edi · validate_edi · map_to_modern · govern_edi

bash
pip install -e .python server.py

Source: README.md at commit 0041f29

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.