EAD Enterprise Suite MCP

Name: EAD Enterprise Suite MCP
Author: g-digital-by-Garrigues

@g-digital-by-Garrigues

EAD Enterprise Suite MCP について

EAD Enterprise Suite MCP bridges MCP clients (Claude, Cursor, etc.) to EAD Trust's complete enterprise platform. The 39 tools cover signature workflows (create → add docs → add participants → coordinate → activate → cancel → retrieve), certified evidence management with sealing a

#digital-trust #e-signature #certified-evidence #certified-notifications #dossier #enterprise #eidas #legal-tech #qualified-trust #garrigues #ead-trust #oidc

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

g-digital-by-Garrigues

投稿者

Hugo Alonso

設定

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

{
  "mcpServers": {
    "ead-enterprise-suite": {
      "command": "npx",
      "args": [
        "-y",
        "@g-digital/mcp-ead-enterprise-suite"
      ],
      "env": {
        "MCP_AUTH_EMAIL": "<your-email>",
        "MCP_AUTH_PASSWORD": "<your-password>"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is EAD Enterprise Suite MCP?

EAD Enterprise Suite MCP exposes the full EAD Trust enterprise Digital Trust platform to MCP clients as 39 tools covering signature workflows, certified evidence, notifications, dossiers, and large‑file uploads.

How to use EAD Enterprise Suite MCP?

Install via npx -y @g-digital/mcp-ead-enterprise-suite or by running the Docker image gdigital/ead-enterprise-suite:1.2.3 with a .env file. Configure authentication using either email+password or OpenID Connect refresh‑token, and choose the stdio transport for local desktop clients or http (Bearer OAuth2) for hosted deployments.

Key features of EAD Enterprise Suite MCP

Full lifecycle of signature workflows (create, add documents/participants, set signing coordinates, activate, cancel, retrieve).
Certified evidence creation, retrieval, listing, sealing, grouping, and multipart large‑file upload via chunked S3 PUT.
Certified notification creation, receiver addition, sending, status polling, and certificate retrieval.
Dossier lifecycle management (create, list, get, templates).
Email+password or OpenID Connect refresh‑token authentication.
Supports both stdio and http (Bearer OAuth2) transports.

Use cases of EAD Enterprise Suite MCP

Automate e‑signature workflows for contracts or approvals within an agent‑based system.
Generate and manage certified evidence (e.g., digital seals, time‑stamped records) for compliance.
Send certified notifications with proof of delivery and status tracking.
Handle large‑file uploads for evidence or documents using chunked multipart uploads.
Integrate enterprise digital trust services into MCP‑compatible assistants or automation pipelines.

FAQ from EAD Enterprise Suite MCP

What authentication methods does EAD Enterprise Suite MCP support?

Two flows are provided: email + password (MCP_AUTH_EMAIL, MCP_AUTH_PASSWORD) and OpenID Connect (recommended for production) using MCP_OPENID_ISSUER, MCP_OPENID_CLIENT_ID, and MCP_OPENID_REFRESH_TOKEN.

What transports are available?

stdio for local desktop clients and http (with inbound Bearer OAuth2) for hosted deployments.

How do I install EAD Enterprise Suite MCP?

Install via npx -y @g-digital/mcp-ead-enterprise-suite or run the Docker image gdigital/ead-enterprise-suite:1.2.3 with an environment file containing authentication variables.

What tools does the server expose?

It exposes 39 tools covering signature workflows, certified evidence, certified notifications, dossier lifecycle, session/auth, and large‑file uploads.

Who maintains this server?

It is maintained by g‑digital by Garrigues (J&A Garrigues, S.L.P.), an eIDAS‑qualified trust services provider operating across the EU. The project is MIT licensed.