MCP.so
ログイン

ediFabric MCP Server認証済み注目

@EdiFabric

基本情報

カテゴリ

開発者ツール

最終更新

ライセンス

NOASSERTION

作者

EdiFabric

投稿者

EdiFabric

ediFabric MCP Server について

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

#edi#x12#hipaa#edi-parser#healthcare#edi-837#medical-claims#edi-validation

ediFabric MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "edifabric": {
      "command": "npx",
      "args": [
        "-y",
        "@edifabric/mcp"
      ],
      "env": {
        "EDIFABRIC_SERIAL": "YOUR_SERIAL",
        "EDIFABRIC_ALLOWED_DIRS": "C:\\EDI"
      }
    }
  }
}

ediFabric MCP Server のツール

7

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.

概要

What is 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, and describe any transaction's structure. It runs ediFabric Native locally; your EDI files stay on your machine.

How to use Edifabric?

The README includes setup instructions such as claude mcp add edifabric -e EDIFABRIC_SERIAL=YOUR_SERIAL -- npx -y @edifabric/mcp.

Key features of Edifabric

  • "Validate claims.837 at SNIP level 4 and explain each error."
  • "Generate a 999 for every file in the inbound folder."
  • "Convert po.edi to JSON, change the quantity on line 2 to 12, and build it back to X12."
  • "What does an 856 in 004010 look like? Create a sample one."
  • double-click the file (installing Claude Desktop registers the .mcpb file type)

Use cases of Edifabric

  • Connect an MCP-compatible client to this repository's service.
  • Review the README-backed setup before enabling it in production.

よくある質問

1

Where is the source code for Edifabric?

The source code is linked from the repository URL on this page.

2

Does Edifabric include a standard MCP config?

If the README contains a parseable MCP configuration block, it is shown in the Config tab.

コメント

「開発者ツール」の他のコンテンツ