Use the API from an AI agent
What it is
You do not have to write the HTTP calls yourself to work with the platform. There is an MCP server — a small program that any MCP-compatible assistant (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code and others) runs on your machine — that exposes the Evidence, Signature and Notification managers as tools the assistant calls on your behalf. It is open source (MIT), published by the platform team on GitHub, and it talks to the same endpoints with the same credentials described in the rest of this site: nothing goes through a third party.
- Source and issues: github.com/g-digital-by-Garrigues/EAD-Factory-MCP
- Package:
@g-digital/mcp-ead-factoryon npm — also on Docker Hub (gdigital/ead-factory), on Smithery, and as an n8n community node (@g-digital/n8n-nodes-ead-factory) for automation flows.
Credentials
The server authenticates exactly as described in Getting started: the OAuth2 client-credentials flow, with a token URL, a client ID and a client secret. They are the same credentials you would use for the REST API, and our team issues them — there is no self-service sign-up. If you do not have them yet, contact us.
Your tenant is read from the token, so there is nothing else to configure. The server runs on your machine and keeps the secret in your local configuration file: treat that file as you would treat any other credential store, and keep it out of version control.
Install the server
Configuration block
Add this block to your assistant's MCP configuration and restart the assistant. The file is
claude_desktop_config.json for Claude Desktop and ~/.claude.json for Claude
Code; other assistants have an equivalent MCP settings file. The block is the same in all of them.
The first start takes a few seconds while npx downloads the package.
{
"mcpServers": {
"ead-factory": {
"command": "npx",
"args": ["-y", "@g-digital/mcp-ead-factory"],
"env": {
"MCP_SVC_TOKEN_URL": "https://{login_url}",
"MCP_SVC_CLIENT_ID": "{clientId}",
"MCP_SVC_CLIENT_SECRET": "{clientSecret}",
"MCP_API_BASE_URL": "https://api.gcloudfactory.com",
"MCP_API_BASE_URL_SIGNATURE": "https://api.eadtrust.gcloudfactory.com/signature-manager"
}
}
}
}
| Variable | What to put in it |
|---|---|
MCP_SVC_TOKEN_URL | The token endpoint from Login — the same URL you would send the client_credentials request to. |
MCP_SVC_CLIENT_ID, MCP_SVC_CLIENT_SECRET | Your credentials. The secret is the only secret value in the block. |
MCP_API_BASE_URL | The gateway host we issued your credentials for, without any manager prefix: the server appends /digital-trust, /notifications and /signature-manager itself. If you leave it out, the server uses built-in defaults that point at production. |
MCP_API_BASE_URL_SIGNATURE | A full base URL for one manager, used as-is. Signature Manager is not always on the same host as the other managers, so set it explicitly to the host the base-paths table gives for your environment rather than relying on the default. |
One server, one environment. A configuration block points at a single environment. If you
work against more than one, add a second entry under mcpServers with another name
(for example ead-factory-int) and its own credentials and hosts.
Check that it works
In Claude Code, /mcp lists the connected servers. Then ask the assistant:
Using the ead-factory MCP server, call ead_factory_help and summarize what this server can do.
ead_factory_help needs no credentials, so it separates an installation problem from a
credentials problem. The first real call — for example «list my case files»,
which the assistant answers with evidence_case_file_search — is what exercises your
credentials. An Upstream HTTP 401 means the token URL, client ID or secret are wrong.
A 404 from the gateway usually means the request did not carry a valid token: see
why a credential that looks right can still fail.
What the tools cover
Every tool is one operation of the REST API, with the same rules, the same identifiers and the same error codes. The assistant chains them; you describe the outcome.
| Manager | Tools | Typical sequence |
|---|---|---|
| Evidence Manager | 41 | evidence_case_file_create → evidence_group_create → evidence_group_evidence_register (then the file bytes go to the upload URL) → evidence_group_close, which seals the group and requests the qualified timestamp → evidence_case_file_report_generate → evidence_case_file_report_pdf_url_get. evidence_create_sealed registers, uploads and seals in one call inside an existing case file. |
| Signature Manager | 13 | create_signature_request → add_document_to_signature_request (plus the upload) → add_signatory_to_document, and add_validator_to_signatory or add_observer_to_document if you need them → activate_signature_request → get_signature_request to follow progress → signature_document_download_url_get. signature_request_full creates, adds documents with their signatories and activates in one call. |
| Notification Manager | 9 | notification_request_create → notification_receiver_add → notification_document_add (plus the upload) → notification_request_send → notification_request_status → notification_certificate_generate → notification_certificate_pdf_url_get. |
| Chat Manager | 0 | Not covered by this version. Use the REST API. |
| Help | 1 | ead_factory_help: an overview of the managers and where to start. Works without credentials. |
Names follow manager_resource_action (evidence_group_close,
notification_receiver_add). A few Signature Manager tools keep older verb-first names
(create_signature_request, add_signatory_to_document,
activate_signature_request…); they are the same operations. Every tool description
states its prerequisites (Requires: evidence_case_file_create → caseFileId), so the
assistant works out the order by itself.
notification_request_send runs as an MCP Task and needs a client that supports
MCP Tasks; from any other client the call fails. Create the request with autosend:
true instead. evidence_create_sealed works from any client: task-aware
clients get a task, the others get the final result synchronously.
The skill: for coding against the REST API directly
If you would rather write the integration yourself and have the assistant help you code it, the same repository ships a Claude Code skill: an integration guide the assistant reads while it writes or debugs code against the REST API — authentication, call order, options, enums and pitfalls for the four managers.
- It lives at
.claude/skills/ead-factory-api/in the repository. It is not in the npm package: clone the repository and open it in Claude Code, or copy that folder into the.claude/skills/folder of your own project. - The same text is readable as a plain document at
docs/api-integration-skill.md. - The npm package does include three Claude Code slash-commands that walk through each flow with the
MCP tools:
/create-internal-evidence,/create-signature-requestand/create-notification-request.
This site describes the behaviour of the services as they are deployed. If the skill and this site disagree, trust this site and tell us.
Limits and where to get help
- Chat Manager has no tools in this version.
- The upload of file bytes to a presigned URL is done by the server for you; the same limits on file size and the same checksum rules as the REST API apply.
- Problems with the server itself — installation, a tool that misbehaves, a wrong description — go to the issues of the repository. Problems with the API, your credentials or your tenant: contact us.