About edi-bridge-mcp
edi-bridge-mcp is an MCP server for bridging EDI X12 and EDIFACT supply-chain messages to ONE OS. It provides tools to parse, validate, map, and govern EDI, including Peppol, ViDA, and SOX contexts.
Key features
- 01Parse EDI messages
- 02Validate EDI messages
- 03Map messages to modern formats
- 04Govern EDI workflows
Use cases
- 01Parse X12 or EDIFACT supply-chain messages
- 02Validate messages before processing
- 03Map EDI data to modern formats
- 04Apply governance to EDI workflows
MCP support
Exposes EDI parsing, validation, mapping, and governance tools to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEedi-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
pip install -e .
python server.py
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.