Groupdocs MCP Server

MCP server for GroupDocs.Comparison — compare documents and inspect source info via AI agents.

Local serverstdio

What is the Groupdocs MCP server?

If you already use Groupdocs, the groupdocs mcp server is the piece that lets your assistant work with it directly. MCP server for GroupDocs.Comparison — compare documents and inspect source info via AI agents.

What the server does

MCP server that exposes GroupDocs.Comparison as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Compare — Compares two documents (source vs target) and produces a marked-up result file, plus a change-count summary and a structured JSON list of the
  • AnalyzeChanges — Returns the differences between two documents as structured data only — the same JSON change list as Compare, but without rendering or saving
  • GetDocumentInfo — Inspects a single source document and returns file type, page count, file size, and per-page dimensions as JSON — without performing a comparison

Credentials and setup notes

Configuration is passed through the environment: GROUPDOCS_MCP_STORAGE_PATH, GROUPDOCS_LICENSE_PATH, GROUPDOCS_MCP_OUTPUT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Groupdocs's toolset — Compare, AnalyzeChanges, GetDocumentInfo — is a fair guide to whether it matches your workflow. It is maintained by groupdocs-comparison; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CompareCompares two documents (source vs target) and produces a marked-up result **file**, plus a change-count summary and a structured JSON list of the changes (type, page, the changed fragment, surrounding source/target text,
AnalyzeChangesReturns the differences between two documents as **structured data only** — the same JSON change list as Compare, but **without** rendering or saving a result file. Cheaper than Compare; use when the user wants to summar
GetDocumentInfoInspects a single source document and returns file type, page count, file size, and per-page dimensions as JSON — without performing a comparison. Useful as a pre-flight check before deciding whether to compare or which

How to install the Groupdocs MCP server

{
  "mcpServers": {
    "groupdocs-comparison": {
      "type": "stdio",
      "command": "dnx",
      "args": ["GroupDocs.Comparison.Mcp", "--yes"],
      "env": {
        "GROUPDOCS_MCP_STORAGE_PATH": "/path/to/documents"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GROUPDOCS_MCP_STORAGE_PATHFilesystem location the server is allowed to use.Optional
GROUPDOCS_LICENSE_PATHFilesystem location the server is allowed to use.Optional
GROUPDOCS_MCP_OUTPUT_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Groupdocs to Compare.
  • Use Groupdocs to AnalyzeChanges.
  • Use Groupdocs to GetDocumentInfo.

Frequently asked questions

It connects Groupdocs to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Compare, AnalyzeChanges, GetDocumentInfo) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Groupdocs directly.