EAD-Factory-MCP: Skill for Claude Code

EAD Factory — API Integration Guide

EAD Factory (a.k.a. GCloud Factory / RPaaS) is not one API but a platform of four independent managers, each with its own OpenAPI contract, its own base URL, and its own operation set. They share auth, URL conventions, and the case-file concept, but you integrate against each manager separately.

Each manager is reached at {host}/{manager-prefix}, then /api/v1/private/.... The host is environment- and tenant-specific (a production host and an int integration host exist); the manager path prefix is stable:

So an evidence call on the integration host looks like https://api.int.gcloudfactory.com/digital-trust/api/v1/private/case-files. Use the host your tenant was issued. All four are OpenAPI 3.0.1 — fetch the live YAML from {host}/swagger/... for exact field schemas; this guide gives you the flows, options, and traps the raw spec doesn't spell out.

1. Authentication — OAuth 2.0 client credentials

EAD Factory has no /session endpoint of its own. Instead, a service integration authenticates against an external OAuth 2.0 identity provider (the tenant's authorization server — e.g. an Okta org) using the client-credentials grant, then presents the resulting bearer token to every manager:

curl -s -X POST "$TOKEN_URL" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d grant_type=client_credentials \
  -d client_id="$CLIENT_ID" \
  -d client_secret="$CLIENT_SECRET" \
  -d scope="$SCOPE"
# → { "access_token": "...", "token_type": "Bearer", "expires_in": 3600, "scope": "..." }