Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-edi parse this X12 850 purchase order"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
EDI meets AI agents: give Claude the ability to read, validate and write EDIFACT, ANSI X12 and cXML.
An MCP server that turns 40 years of B2B message formats into something an AI agent can work with natively — built by an EDI consultant with 20 years of EDIFACT/X12/cXML integrations behind him.
The parsers are written by hand — no EDI library, no XML dependency. Tokenizing UNA service strings, deducing X12 delimiters from the ISA header, verifying UNT/SE/GE/UNZ/IEA control counters: that is the point. The only runtime dependencies are the official MCP SDK and zod.
git clone https://github.com/MaestroMed/mcp-edi.git
cd mcp-edi
npm install && npm run buildAdd to claude_desktop_config.json (or .mcp.json for Claude Code):
{
"mcpServers": {
"edi": {
"command": "node",
"args": ["/absolute/path/to/mcp-edi/dist/server.js"]
}
}
}Restart the client — six EDI tools appear.
Related MCP server: encoding-devops
Tool | What it does |
| Raw UN/EDIFACT → structured JSON. UNA-aware (custom separators, release character), UNB/UNZ + UNH/UNT envelopes, type recognition (ORDERS, DESADV, INVOIC, ORDRSP...), UNT/UNZ counter checks. |
| Raw ANSI X12 → structured JSON. Delimiters deduced from the ISA itself, ISA/GS/ST hierarchy, type recognition (850, 856, 810, 997...), SE/GE/IEA counter and control-number checks. |
| cXML e-procurement → JSON: PunchOutSetupRequest/Response and OrderRequest, From/To/Sender credentials, items and amounts. SharedSecret values are detected but never echoed. |
| Auto-detects the standard, verifies envelope structure, mandatory segments per message type, and every counter. Returns actionable errors/warnings: segment, position, expected, found. |
| Built-in dictionary — 35 EDIFACT + 28 X12 segments. |
| Simple JSON (parties, dates, line items) → valid EDIFACT ORDERS D.96A interchange with correct envelopes, escaping and counters. Round-trips through |
You: Our supplier says our order file is broken. Here it is: (pastes EDIFACT)
Claude (calls
validate_message): The interchange is invalid — two problems:
UNTdeclares 18 segments but the message contains 20 (UNT_COUNT_MISMATCH, position 21). Your mapper is not counting the twoPRIsegments added last week.
UNZcontrol referenceICR0002does not matchUNBreferenceICR0001— the envelope was rebuilt from a stale template.You: Fix the counters and show me what line 2 orders.
Claude (calls
parse_edifact): Line 2 orders 24 PCE of EAN8718123400022("Industrial widget size L") at 15.75 EUR net.
EDI is not legacy — it is the installed base of world trade. Every retailer, carrier and marketplace still speaks EDIFACT or X12, and every e-procurement platform speaks cXML. What is changing is who reads these messages: agents are starting to negotiate, order and invoice on behalf of companies.
Agent-to-agent commerce will not replace the EDI rails; it will drive them. The missing piece is a translation layer the agent can trust — deterministic parsing, real envelope validation, counters checked, nothing hallucinated. That layer is what this server provides: the LLM does the reasoning, the parsers do the arithmetic.
npm test # vitest — 81 tests: nominal, custom UNA separators, truncated
# messages, wrong counters, generate→parse round-trips
npm run build # tsc, strict mode
npm run smoke # spawns the compiled server, runs the MCP handshake on stdio,
# checks tools/list and a live tools/callsamples/ contains six anonymized messages (ACME Corp / Globex — fictional data only): ORDERS, DESADV, INVOIC, 850, 856, PunchOutSetupRequest. Every sample validates clean; the test suite enforces it.
AS2 headers inspector — MDN, MIC and disposition debugging for transport-level issues
Peppol UBL — parse and validate BIS 3.0 invoices/orders
SAP IDoc — ORDERS05/DESADV parsing from flat-file IDocs
MIT — Mehdi Nafaa
Explain an EDI segment tag in plain English: role, key elements and a realistic example. Covers 35 EDIFACT segments (UNB, BGM, DTM, NAD, LIN, QTY...) and 28 X12 segments (ISA, ST, BEG, N1, PO1, HL...). Tags that exist in both standards (DTM, LIN) return both entries unless a standard is specified.
Inputs: tag (required), standard.
Generate a syntactically valid EDIFACT ORDERS D.96A interchange (UNA + UNB...UNZ) from a simple JSON order description: parties, dates, currency and line items. Envelopes, escaping and UNT/UNZ counters are computed automatically; the output round-trips through parse_edifact with zero issues.
Inputs: items (required), sender (required), orderDate (required), recipient (required), +9 more.
Parse a cXML e-procurement document (PunchOutSetupRequest, PunchOutSetupResponse, OrderRequest) into structured JSON: From/To/Sender credentials, punchout session data, order header with totals and addresses, and line items with quantities and prices. SharedSecret values are detected but never echoed.
Inputs: message (required).
Parse a raw UN/EDIFACT interchange into structured JSON: UNA-declared separators, UNB/UNZ envelope, one entry per UNH/UNT message with decomposed segments (composite and simple elements), message type recognition (ORDERS, DESADV, INVOIC, ORDRSP...) and UNT/UNZ counter verification. Returns issues with segment, position, expected and found values.
Inputs: message (required).
Parse a raw ANSI X12 interchange into structured JSON. Delimiters are deduced from the ISA segment itself (element separator = 4th character, component separator = ISA16, segment terminator = the character after ISA16). Returns the ISA/GS/ST hierarchy with decomposed segments, transaction type recognition (850, 856, 810, 997...) and SE/GE/IEA counter and control-number verification.
Inputs: message (required).
Detect the EDI standard (EDIFACT, X12 or cXML), verify the envelope structure, the mandatory segments for the recognized message type, and all control counters. Returns an actionable list of errors and warnings — each with segment, position, expected and found — plus a one-line summary.
Inputs: message (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a distinct purpose: parsing three different EDI standards, validation, segment explanation, and generation. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores: parse, validate, explain, generate. No mixing of conventions.
Six tools cover the core EDI workflows (parse, validate, explain, generate) for the main standards without being excessive or sparse.
Covers parsing for EDIFACT, X12, and cXML, validation across all, explanation, and generation for EDIFACT. Missing generation for X12 and cXML is a minor gap.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Hosted Amazon Seller and Vendor MCP server for Claude, ChatGPT, Cursor, Codex, Gemini, Copilot.
Cloud-hosted MCP server for secure AI access to enterprise data sources via CData Connect AI.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
