Changelog

Release history for the ECGrid MCP server.

Current version: 2.1.0

[2.1.0] — 2026-08-11

connectivity_ecgrid-id_set-id-status — suspend or activate an EDI ID.
connectivity_parcel_send-test-parcel — send a test file between two ECGrid IDs.
connectivity_parcel_cancel-parcel — cancel a pending parcel.
connectivity_interchange_cancel-interchange — cancel a pending interchange.

Breaking. The partnership delivery-test tool is replaced by the new send-a-test-file tool: takes two ECGrid IDs instead of a partnership ID, requires an explicit file format, and no alias exists for the old name.
Sending a test file no longer waits for the outcome — it returns the parcel number, and you look that up to see whether it arrived.
A test file aimed at an ECGrid ID that cannot receive traffic is now refused outright instead of producing a parcel that silently goes nowhere.

A new client can now ask the server which protocol versions it speaks before it has been given an API key. That one question — and only that one — is answered without a credential; everything else still needs one, and the answer contains no tool, resource, or prompt names.
Tool, prompt and resource listings — and the content behind a resource — now tell newer clients how long the answer may be reused and that it belongs to that caller alone. Older clients see no change.
Deleting a mailbox or an EDI ID, suspending a mailbox, and cancelling a partnership now ask a person to confirm, in the client's own prompt, before anything happens. Clients that cannot ask keep using the confirmation value passed with the call, exactly as before.

The public server description pages now list protocol versions in two groups: the ones a client selects up front, and the ones settled during connection. Capabilities are reported in the standard Model Context Protocol format instead of a simplified yes/no list. Breaking for anything reading those fields directly — see Removed.
Upgraded to version 2.0 of the Model Context Protocol SDK. The server now also speaks the newest protocol revision (2026-07-28) while continuing to accept older clients exactly as before — every tool, its inputs, and its outputs are unchanged.
The tool list is now returned in alphabetical order, so it reads the same way every time and groups tools by product and area.
Asking for a glossary term, parcel status, or interchange status that does not exist now comes back as "you asked for something that isn't there" instead of looking like a server fault.
connectivity_partner_get-partner-by-id — renamed input parameter partnerId → interconnectId to match the naming used by all other partner tools (list-partners, add-partner, complete-partner, cancel-partner, check-partner-config, test-partner-delivery). The parameter description notes that interconnectId and partnerId are the same value in ECGrid contexts.

Two fields on the public server description pages that described nothing real: a protocol version stamp that matched no published revision, and a "sampling" capability that belongs to clients rather than servers. Replaced by the version groups above.

Simplify integration — six read-only tools for browsing a Simplify account: flows, connections, lookup tables (and their values), and maps (and their links). Each has a matching UI panel and is only visible to users with the right Simplify permission.

Simplify sign-in is documented as a personal access token, not a generic API key.
Simplify tool calls are now recorded in the audit log, including failed sign-ins with a revoked or expired token.

GPA (DataSync) integration — five read-only tools for Global Product Access data: datasync_product_list-products, datasync_product_get-product-details, datasync_catalog_list-catalogs, datasync_catalog_list-products, and datasync_company_list-companies (Host / NetworkAdmin only). Authenticates via the X-DataSync-API-Key header (GPA Personal Access Token); acting-on-behalf uses X-Company-Id.
MCP Apps (interactive UI) — React + Vite panels served as ui:// resources for mailbox, partner, EDI-ID, transaction, interchange, parcel, and GPA product/catalog results.
Role-based tool filtering — the tool list is filtered per caller so a client only sees the tools it is entitled to use.
Discovery & marketing surface — branded GET / index, GET /tools (human-readable) and GET /tools.json (machine-readable, CORS), llms.txt, /.well-known/mcp capability advertisement, and a SEP-1649 server-card.json.
MCP tool annotations (readOnly / idempotent / destructive / openWorld) on all connectivity tools.
connectivity_mailbox_list-mailboxes tool; aggregate transaction search.
Live-backend smoke test suite.

Audit — cross-product caller identity captured on every tool, resource, and prompt invocation; durable audit index enabled in Production.
Discovery routes are exempt from the auth middleware.
ListPartners filters extended; null filters are omitted rather than sent as JSON null.

Resources and Prompts surfaces (resources/list/read, prompts/list/get) with per-caller entitlement gating and audit.

MCP Foundation — ASP.NET Core MCP server (net10.0) with the connectivity and translation tool set, APIKey/JWT authentication, inbound sanitization, unified error envelope, Serilog + Elasticsearch sink, Azure Key Vault configuration, and the CI/CD build/release pipelines.