Where is the source code for Edifabric?
The source code is linked from the repository URL on this page.
@EdiFabric
基本情報
The ediFabric MCP server lets AI assistants validate X12 and HIPAA EDI files up to SNIP level 4 and explain each error, convert EDI to JSON and back, generate 999 and 997 acknowledgments, split files into transactions, a
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"edifabric": {
"command": "npx",
"args": [
"-y",
"@edifabric/mcp"
],
"env": {
"EDIFABRIC_SERIAL": "YOUR_SERIAL",
"EDIFABRIC_ALLOWED_DIRS": "C:\\EDI"
}
}
}
}Converts an EDI file (X12, including HIPAA) to JSON and saves it to a file. Returns a summary of its contents. The JSON uses the same property names as describe_spec, and build_edi converts it back.
Validates an EDI file (X12, including HIPAA) against its implementation guide, up to the chosen SNIP level. Returns each error with the text of the segment, and its segment and element position. Doesn't write any files.
Validates an EDI file and saves the acknowledgment for it. For X12: a 999 by default, or a 997, with a TA1 when the interchange asks for one. Returns the validation errors too.
Converts EDI JSON, as produced by parse_edi or written to match describe_spec, to an EDI file. The segments are written as they are in the JSON, so include the trailer segments with the correct counts, and run validate_edi on the result.
Splits an EDI file into one file per transaction, such as one claim batch into separate files. Each file keeps the original envelopes, with their counts set to 1.
Describes a transaction (X12, including HIPAA) from the model parse_edi and build_edi use: a local or custom model in the map file, otherwise the standard model. The outline lists its loops and segments with the JSON property names. Give segment for one segment's elements, types, lengths, codes and syntax rules. Set output to skeleton for JSON to fill in and pass to build_edi.
Shows the license and how it's checked, where models come from and which folders the tools can use. Use it when a tool reports a setup problem.
The ediFabric MCP server lets AI assistants validate X12 and HIPAA EDI files up to SNIP level 4 and explain each error, convert EDI to JSON and back, generate 999 and 997 acknowledgments, split files into transactions, and describe any transaction's structure. It runs ediFabric Native locally; your EDI files stay on your machine.
The README includes setup instructions such as claude mcp add edifabric -e EDIFABRIC_SERIAL=YOUR_SERIAL -- npx -y @edifabric/mcp.
The source code is linked from the repository URL on this page.
If the README contains a parseable MCP configuration block, it is shown in the Config tab.

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Agent-Native Terminal
Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
コメント