Ead Factory Mcp
@g-digital-by-Garrigues
EAD Factory MCP — Digital Trust services APIs for your agents. Bridges any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.) to Garrigues' Evidence Manager + Signature Manager APIs.
Overview
What is EAD Factory MCP Server?
EAD Factory MCP Server is a Model Context Protocol server that provides qualified evidence, signature, notifications, and chat capabilities to AI agents. It integrates with the EAD Factory digital trust platform.
How to use EAD Factory MCP Server?
Install via npx -y @g-digital/mcp-ead-factory or Docker, then configure the required environment variables (MCP_SVC_TOKEN_URL, MCP_SVC_CLIENT_ID, MCP_SVC_CLIENT_SECRET). Credentials are obtained from https://digitaltrust.gcloudfactory.com. Preconfigured examples are provided for Claude Desktop, Claude Code, Cursor, Windsurf, Cline, VS Code, JetBrains, and Zed. Bundled Claude Code slash-commands (/create-internal-evidence, etc.) offer workflow guides.
Key features of EAD Factory MCP Server
- 64 tools for evidence, signature, notifications, and chat
- Available via npm, Docker, Smithery, and n8n
- Bundled Claude Code slash-command workflows
- OAuth2 client_credentials authentication
- Configurable HTTP transport with security features
- Docker image for containerized deployment
Use cases of EAD Factory MCP Server
- Automate evidence creation and case file management
- Send qualified signature requests via AI agents
- Trigger notification requests through AI chat workflows
- Search and manage evidence records programmatically
- Manage digital trust processes without manual intervention
FAQ from EAD Factory MCP Server
What credentials are required?
You need OAuth2 client credentials (client ID, client secret, and token URL). Obtain them from https://digitaltrust.gcloudfactory.com.
Which environment variables are mandatory?
MCP_SVC_TOKEN_URL, MCP_SVC_CLIENT_ID, and MCP_SVC_CLIENT_SECRET are required. Optional variables allow customizing API base URLs, HTTP settings, and
