Ead Factory
Wire EAD Factory digital-trust service APIs into your agent so you can prototype evidence-manager and full-flow signing integrations during product build.
Overview
EAD Factory MCP is an MCP server for the Build phase that connects your agent to EAD Digital Trust factory APIs including Evidence Manager and Okta-backed flows.
What is this MCP server?
- EAD Factory digital trust services exposed for agent orchestration
- Evidence Manager integration via configurable API_BASE_URL
- Full-flow helpers with FULL_FLOW_EMAIL_BASE and FULL_FLOW_FILE_PATH env configuration
- Okta client_credentials via OKTA_CLIENT_ID and OKTA_CLIENT_SECRET
- npm @g-digital/mcp-ead-factory version 1.0.8 with optional HTTP_PORT when TRANSPORT=http
- npm package @g-digital/mcp-ead-factory version 1.0.8
- Required env vars include API_BASE_URL, Okta client ID/secret, and full-flow email/file paths
- HTTP_PORT applies when TRANSPORT=http; stdio is the default package transport
What problem does it solve?
Integrating digital-trust APIs means juggling Okta secrets, evidence endpoints, and test flow fixtures without a single agent-facing interface.
Who is it for?
Solo legaltech or regtech builders implementing EAD Trust backends who want MCP-driven API exploration and integration scaffolding.
Skip if: Builders without Okta and Evidence Manager access, or teams that only need finished enterprise UI flows without custom API wiring.
What do I get? / Deliverables
After setup, your agent can call EAD Factory trust services using your configured API base URL, Okta credentials, and full-flow defaults.
- MCP-accessible EAD Factory trust API tools for your agent
- Repeatable full-flow signing test configuration via environment variables
- Integration baseline for Evidence Manager-backed features
Recommended MCP Servers
Journey fit
Factory-oriented trust APIs are adopted while you integrate external compliance services into backends and agent tooling. Integrations captures MCP servers that front REST-style trust APIs (Evidence Manager, Okta client credentials) for development workflows.
How it compares
Composable trust API MCP for builders, not the all-in-one Enterprise Suite dossier product surface.
Common Questions / FAQ
Who is ead-factory for?
It is for developers integrating EAD Digital Trust factory services who want agents to invoke Evidence Manager and related APIs through MCP.
When should I use ead-factory?
Use it during Build when you are connecting trust APIs, Okta auth, and repeatable full-flow test paths into your app or agent automation.
How do I add ead-factory to my agent?
Configure API_BASE_URL, FULL_FLOW_EMAIL_BASE, FULL_FLOW_FILE_PATH, HTTP_PORT (if using HTTP transport), OKTA_CLIENT_ID, and OKTA_CLIENT_SECRET, then add @g-digital/mcp-ead-factory (1.0.8) as a stdio or HTTP MCP server in your client.