26.7.3

26.7.3 — Full configuration surface in install snippets (docs/infra only)

What changed

No server code changes — the bump republishes so the refreshed README (install
buttons above the fold, Codex/Windsurf guides, fixed one-click links) reaches the
NuGet package page, Docker/GHCR, and the MCP Registry.

• Every install snippet and one-click deeplink (VS Code / Cursor buttons, Claude
  Desktop/Code, VS Code, VS 2022, Cursor, Windsurf, Cline, Rider, Codex) now
  pre-fills all supported environment variables so users see the full
  configuration surface in the install dialog:
  • GROUPDOCS_MCP_STORAGE_PATH — placeholder documents folder
  • GROUPDOCS_MCP_OUTPUT_PATH — same folder as storage by default
  • GROUPDOCS_LICENSE_PATH — empty by default (evaluation mode)
• Verified in GroupDocs.Mcp.Core's LicenseManager: an empty license path is
  handled identically to an unset one (string.IsNullOrEmpty guard → evaluation
  mode with a log warning; a wrong path only logs; SetLicenseFromPath is wrapped
  in try/catch) — an empty value can never fail the server.

Migration / impact

Drop-in — the server binary is identical apart from the version stamp.

Full Changelog: 26.7.2...26.7.3

26.7.2

26.7.2 — Docker-first docs & one-click install uplift (docs/infra only)

What changed

Rollout of the org-wide MCP repo improvement plan, adapted for this Docker-first
product (the packed tool exceeds NuGet.org's 250 MB limit — no dnx/NuGet path).
No server code changes.

• README rewritten Docker-first: the dnx / dotnet tool install instructions —
  which could not work, since the package is not on NuGet — are replaced by the
  GHCR docker run path with the why-and-when-it-reverts note. Claude Desktop and
  VS Code sections now show docker-command configs. Added badge row (GHCR, MCP
  Registry OCI, Tests CI, MIT), one-click VS Code / Cursor buttons (docker-mode
  deeplinks), and a Licensing section (evaluation limits, license mounting,
  temporary-license / purchase links).
• install/config.json + docker-aware install/generate-install-links.ps1
  (superset of the wave-1 generator: emits docker-command snippets for every
  client) + CI drift guard in build_packages.yml.
• Hygiene: SECURITY.md, CONTRIBUTING.md, issue templates, smithery.yaml
  (docker command), llms.txt rewritten Docker-first with licensing, .vscode/mcp.json
  published (docker) entry, GitHub topics.

Why

The published install instructions actively misled users toward a dnx command that
fails (no NuGet package exists). Docker-first docs match how the product actually ships.

Migration / impact

Drop-in — the server binary is identical to 26.7.1 apart from the version stamp.

Full Changelog: 26.7.1...26.7.2

26.7.1

26.7.1 — Docker-first (OCI) publishing; NuGet size-gate

What changed

• Bumped the MCP package version from 26.7.0 to 26.7.1 (CalVer), including .mcp/server.json (both version fields) and the OCI identifier tag (ghcr.io/groupdocs-total/total-net-mcp:26.7.1).
• .mcp/server.json publishes as an OCI package (registryType: "oci", identifier: ghcr.io/groupdocs-total/total-net-mcp:<version>) instead of NuGet — GroupDocs.Total packs well over NuGet.org's 250 MB limit.
• publish_prod.yml: added a "Check nupkg size vs NuGet limit" step that sets an oversize output at the 250 MB threshold, and guarded the CodeSign / NuGet-push steps with if: oversize != 'true'. When oversized, the release still produces the GitHub Release, the Docker/GHCR image, and the MCP Registry entry (which waits on the GHCR image instead of the NuGet index).
• docker/Dockerfile: added LABEL io.modelcontextprotocol.server.name="io.github.groupdocs-total/groupdocs-total-mcp" (required for OCI registry validation) plus a revert-to-NuGet pointer comment.

Why

GroupDocs.Total's engine set makes the packed tool exceed NuGet.org's hard 250 MB limit, so a NuGet-tool install is impossible. Publishing the server as a Docker/OCI image (GHCR) and registering it in the MCP Registry via registryType: "oci" delivers the same server without the size ceiling. The size-gate keeps a single publish pipeline shared with the NuGet-sized products: it auto-detects oversize and skips only the NuGet-specific steps.

Migration / impact

Install via Docker/OCI rather than dnx/NuGet. Revert notes in publish_prod.yml and the Dockerfile describe restoring the NuGet path once (if) the packed size drops under 250 MB.

Full Changelog: https://github.com/groupdocs-total/GroupDocs.Total.Mcp/commits/26.7.1