Ead MCP Server

EAD Factory MCP — Digital Trust services APIs for your agents. Exposed over MCP by the ead mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This repo is the implementation of the g-digital MCP Distribution System — an internal pipeline that takes an MCP source folder, validates it, and publishes it to npm, Docker Hub, the MCP Official Registry, Smithery, Docker MCP Catalog, Cline Marketplace, , and (for Track B) n8n's npm community.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• mcp-pipeline.yaml — registry of MCPs the pipeline knows how to publish, keyed by kebab-case id. Each entry's only required field is repo_url. Everything else moves to
• pending-to — publish// is transient at workflow time: the checkout-mcp-source composite action clones the MCP

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ead mcp server does with a few real requests.

When to reach for it

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ead's toolset — mcp-pipeline.yaml, pending-to — is a fair guide to whether it matches your workflow. It is maintained by g-digital-by-Garrigues; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.