​

EDI MCP Server

​

What it exposes

​

Build

cd mcp
npm install
npm run build      # → dist/index.js

​

Configure

​

Claude Desktop

{
  "mcpServers": {
    "stateset-edi": {
      "command": "node",
      "args": ["/absolute/path/to/stateset-edi/mcp/dist/index.js"],
      "env": {
        "EDI_API_BASE": "https://your-edi-host",
        "EDI_API_TOKEN": "your-admin-token"
      }
    }
  }
}

​

Claude Code

claude mcp add stateset-edi \
  --env EDI_API_BASE=https://your-edi-host \
  --env EDI_API_TOKEN=your-admin-token \
  -- node /absolute/path/to/stateset-edi/mcp/dist/index.js

​

Try it

List our trading partners, then process this 850 and show me the signed event it produced.

Show the deductions summary and dispute the largest open chargeback.

Run standard certification for walmart-us and tell me if it published a template.

Run edi_demo_order_to_invoice_flow and summarize the generated PO, shipment, invoice, carton labels, and final 856/810 reconciliation status.

​

Notes

• Transport is stdio — the universal local form. The same tool definitions can be served over Streamable HTTP for a hosted/remote MCP callable by cloud agents and deployable to Kubernetes alongside the gateway.
• The server holds no state and stores no credentials beyond the environment variable. Every call is a direct, authenticated request to the gateway.
• Scope an agent down by giving it a partner API key instead of the admin token — it will only reach that partner’s own routes.

​

Related

• Overview
• Operations
• MCP Integration Guide