EAD_Enterprise_Suite_MCP: Command for Claude Code

Evidence Lifecycle (EAD Enterprise Suite)

Create and manage certified evidence chains, including large file uploads.

Key concepts

• Evidence group: A container that groups related evidence items. Must exist before adding evidence.
• evidenceType: FILE (documents), PHOTO, VIDEO, or WEB_PLUGIN.
• custodyType: INTERNAL (EAD stores the file) or EXTERNAL (you store the file, EAD certifies the hash).
• Sealing: Certifies the entire group — timestamped and legally binding. Long-running (MCP task stays open until complete).
• Large files: Files ≥ 10 MB require the multipart upload flow via large_evidence_upload_initiate.

IDs you need before starting

• caseFileId — from case_file_list

---

Standard flow (< 10 MB)

Step 1 — Create evidence group

evidence_group_create(
  id: "<new-uuid>",
  caseFileId: "<uuid>",
  evidenceType: "FILE",            # FILE | PHOTO | VIDEO | WEB_PLUGIN
  name: "Group name (max 64 chars)",
  description: "Optional description (max 160 chars)"
)

Step 2 — Create evidence item

evidence_create(
  id: "<new-uuid>",
  caseFileId: "<uuid>",
  evidenceGroupId: "<group-uuid>",
  title: "Evidence title (max 128 chars)",
  fileName: "document.pdf",
  hash: "<sha256-hex>",           # SHA-256 hex digest of the file
  custodyType: "INTERNAL"         # INTERNAL | EXTERNAL
)

Returns { uploadFileUrl: "<presigned-s3-url>", ... }.

Shortcut for local files — evidence_upload: instead of hashing + evidence_create + manual PUT, call evidence_upload with the local file (filePath in stdio mode, or contentBase64) plus caseFileId, evidenceGroupId, title, fileName. It computes the SHA-256, registers the evidence, and uploads the bytes in one step. (filePath is rejected in HTTP mode — use contentBase64 there.)

Step 3 — Upload the file

PUT <uploadFileUrl>
Content-Type: application/octet-stream
x-amz-checksum-sha256: <base64-encoded SHA-256>   # base64 of the same hash (not hex)
Body: <raw file bytes>