Ead Enterprise Suite
Run EAD Trust enterprise signature flows, certified evidence, and dossiers from your agent when you ship contract-heavy B2B or legaltech features.
Overview
EAD Enterprise Suite MCP is an MCP server for the Ship phase that runs full EAD Trust signature workflows and certified evidence dossiers from your agent.
What is this MCP server?
- Full EAD Enterprise Suite signature workflows exposed as MCP tools
- Certified evidence and dossier operations via EAD Trust / GoCertius backends
- stdio npm package @g-digital/mcp-ead-enterprise-suite at version 1.3.9
- OpenID Connect auth with required MCP_AUTH_EMAIL, MCP_AUTH_PASSWORD, and refresh token env vars
- Enterprise credential acquisition documented at eadtrust.eu LegalTech Enterprise Suite
- Published version 1.3.9 on npm as @g-digital/mcp-ead-enterprise-suite
- Five required auth-related environment variables including OpenID refresh token
- stdio transport per MCP server schema 2025-12-11
What problem does it solve?
Small teams integrating qualified signatures must repeatedly context-switch between trust portals and custom APIs instead of driving enterprise legal flows from the IDE.
Who is it for?
Legaltech or B2B solo builders with existing GoCertius / Enterprise Suite accounts who need agent-driven qualified signature and evidence automation.
Skip if: Hobby MVPs, builders without EAD credentials, or anyone who only needs informal DocuSign-style clicks without certified evidence.
What do I get? / Deliverables
After configuration, your agent can invoke Enterprise Suite trust operations with OpenID-authenticated access to certified evidence and dossiers.
- Agent-driven enterprise signature and evidence workflows
- MCP tools for dossiers and certified evidence from EAD Trust
- Auditable automation hooks for B2B contract pipelines
Recommended MCP Servers
Journey fit
How it compares
Regulated trust-platform MCP, not a generic document-signing skill or a local PDF helper.
Common Questions / FAQ
Who is ead-enterprise-suite for?
It is for developers and operators who already use EAD Trust Enterprise Suite and want MCP access to full signature workflows, certified evidence, and dossiers.
When should I use ead-enterprise-suite?
Use it in Ship when contracts or compliance artifacts must use EAD’s enterprise certified paths, not for early prototypes with informal signing.
How do I add ead-enterprise-suite to my agent?
Obtain Enterprise Suite credentials from EAD Trust, set MCP_AUTH_EMAIL, MCP_AUTH_PASSWORD, MCP_OPENID_CLIENT_ID, MCP_OPENID_ISSUER, and MCP_OPENID_REFRESH_TOKEN, then register @g-digital/mcp-ead-enterprise-suite (1.3.9) as a stdio MCP server.