EAD Enterprise Suite MCP

Created By
g-digital-by-Garrigues10 days ago
EAD Enterprise Suite MCP bridges MCP clients (Claude, Cursor, etc.) to EAD Trust's complete enterprise platform. The 39 tools cover signature workflows (create → add docs → add participants → coordinate → activate → cancel → retrieve), certified evidence management with sealing and grouping plus multipart large-file uploads, certified notifications (create → add receivers → send → status → certificate retrieval), dossier lifecycle (create → list → get → templates), and session / authentication management (email/password or OpenID Connect refresh-token). Built by g-digital by Garrigues (J&A Garrigues, S.L.P.), an eIDAS-qualified trust services provider. Two transports: stdio for local clients, HTTP with Bearer OAuth2 for hosted deployments.
Overview

EAD Enterprise Suite MCP exposes the full EAD Trust enterprise Digital Trust platform to MCP clients as 39 tools — signature workflows, certified evidence, notifications, dossiers, and large-file uploads.

What it does

  • Signature workflows — full lifecycle: create → add documents → add participants → set signing coordinates → activate → cancel or retrieve. Includes massive participant creation, validators, observers, document handling.
  • Certified evidence — create, retrieve, list, seal, group; multipart large-file upload via initiate + complete with chunked S3 PUT.
  • Certified notifications — create → add receivers → send → poll status → retrieve certificate.
  • Dossier lifecycle — create, list, get, templates.
  • Session / auth — email+password or OpenID Connect refresh-token.

Install

npx -y @g-digital/mcp-ead-enterprise-suite

Or via Docker:

docker run --rm -it --env-file .env gdigital/ead-enterprise-suite:1.2.3

Auth

Two flows:

  • Email + password: MCP_AUTH_EMAIL, MCP_AUTH_PASSWORD.
  • OpenID Connect (recommended for production): MCP_OPENID_ISSUER, MCP_OPENID_CLIENT_ID, MCP_OPENID_REFRESH_TOKEN.

Transports

stdio for local desktop clients; http (Bearer OAuth2 inbound) for hosted deployments.

Maintainer

g-digital by Garrigues (J&A Garrigues, S.L.P.) — an eIDAS-qualified trust services provider operating across the EU. MIT licensed. Source repo.

Also published on npm, Docker Hub, the MCP Official Registry, Smithery, and as an n8n community node.

Server Config

{
  "mcpServers": {
    "ead-enterprise-suite": {
      "command": "npx",
      "args": [
        "-y",
        "@g-digital/mcp-ead-enterprise-suite"
      ],
      "env": {
        "MCP_AUTH_EMAIL": "<your-email>",
        "MCP_AUTH_PASSWORD": "<your-password>"
      }
    }
  }
}
Project Info
Created At
10 days ago
Updated At
10 days ago
Author Name
g-digital-by-Garrigues
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Thousand Api

2 hours ago
Hellogrowthcrm

18 hours ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

a day ago