Ead MCP Server

EAD Enterprise Suite MCP — signature workflows, evidence, notifications, dossiers for enterprises. The ead mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• Skill — ** .claude/skills/gocertius-suite-api/SKILL.md — open this repo in Claude Code and it is available
• evidence_create — Registers a NEW evidence record inside an evidence group. Requires: evidence_group_create → evidenceGroupId, case_file_create → caseFileId. Generate
• evidence_list — Lists all evidence records in a specific evidence group. Requires: caseFileId and evidenceGroupId. Returns paginated list with IDs, titles, status
• evidence_seal — Seals an evidence group and triggers qualified TSP timestamping. Requires: all INTERNAL evidence records in the group have already been uploaded to
• evidence_get — Retrieves a specific evidence record. Requires: evidence_create → evidenceId, evidence_group_create → evidenceGroupId, case_file_create → caseFileId
• evidence_group_create — Creates an evidence group inside a case file. Requires: case_file_create → caseFileId. Generate a UUID v4 for id. Set evidenceType to FILE, PHOTO
• evidence_group_list — Lists all evidence groups in a case file with their current status (OPEN, CLOSING, CLOSED). Use to find an existing group or check which groups are
• dossier_create — Creates a dossier to aggregate certified evidence groups into a single tamper-evident PDF. Requires: case_file_create → caseFileId. Evidence groups
• dossier_update — Updates the metadata of an existing dossier. Requires: dossier_create → dossierId, caseFileId. Only available while dossier is in DRAFT status
• dossier_certify — Certifies a dossier, generating a tamper-evident PDF and locking all linked evidence. Requires: dossier_create → dossierId, dossier_evidence_link
• dossier_list — Lists all dossiers in a case file. Requires: caseFileId. Returns paginated list with IDs, names, status, and creation dates. Use to monitor
• dossier_get — Retrieves full details of a specific dossier including status, linked evidence, and download URLs. Requires: caseFileId and dossierId

Configuration

You will need 8 environment variables: MCP_AUTH_EMAIL, MCP_AUTH_PASSWORD, MCP_ALLOW_INSECURE_FILE_URL, MCP_API_BASE_URL, MCP_AUTH_USER_KEY, MCP_HTTP_HOST, MCP_SVC_INTROSPECT_URL, MCP_SVC_CLIENT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ead's toolset — Skill, evidence_create, evidence_list and 11 more — is a fair guide to whether it matches your workflow. It is maintained by g-digital-by-Garrigues; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ead's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ead.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ead mcp server does with a few real requests.