GroupDocs.Comparison MCP Server
Enables AI agents to compare documents, analyze changes, and retrieve document info using GroupDocs.Comparison. Supports various formats and includes licensing for production use.
README
GroupDocs.Comparison MCP Server
MCP server that exposes GroupDocs.Comparison as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents.
<!-- TODO(manual): record 30s demo per improvement-plan M1 -->
<!--
-->
Installation
<!-- install-buttons:start - generated by install/generate-install-links.ps1; do not edit by hand -->
One-click installs pre-fill every supported setting: edit the placeholder documents folder after install (output defaults to the same folder); an empty GROUPDOCS_LICENSE_PATH runs in evaluation mode - point it at your license to lift limits.
More clients - ready-made configs for Claude Code, Codex CLI, Visual Studio 2022, Cursor, Windsurf, Cline, and JetBrains Rider live in
install/generated/. <!-- install-buttons:end -->
Requires .NET 10 SDK.
Run directly with dnx (recommended — no install step):
dnx GroupDocs.Comparison.Mcp --yes
Pulls the latest stable release on every invocation. To pin to a specific
version (recommended for shared configs and CI), append @<version>:
dnx GroupDocs.Comparison.Mcp@26.7.4 --yes
Or install as a global dotnet tool:
dotnet tool install -g GroupDocs.Comparison.Mcp
groupdocs-comparison-mcp
Or run via Docker:
docker run --rm -i \
-v $(pwd)/documents:/data \
ghcr.io/groupdocs-comparison/comparison-net-mcp:latest
Native prerequisites
The underlying GroupDocs engine uses System.Drawing (GDI+) for some
operations. When you run the server natively (via dnx or the global
dotnet tool) on Linux or macOS, install the native libgdiplus library first:
| Platform | Setup |
|---|---|
| Windows | Nothing — GDI+ is built into the OS. |
| Linux | sudo apt-get install -y libgdiplus libfontconfig1 ttf-mscorefonts-installer |
| macOS | brew install mono-libgdiplus |
| Docker | Nothing — the image already bundles libgdiplus. |
Skipping this on Linux/macOS surfaces as DllNotFoundException: libgdiplus in
the tool response. The simplest zero-setup option on Linux/macOS is the
Docker image.
Available MCP Tools
| Tool | Description |
|---|---|
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 changes (type, page, the changed fragment, surrounding source/target text, table cell, style changes). Use when the user wants the rendered diff document. Supports PDF, Word, Excel, PowerPoint, ODT, RTF, TXT, HTML, and 30+ more formats; optional sourcePassword / targetPassword cover protected documents. |
AnalyzeChanges |
Returns 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 summarize, explain, or reason about what changed rather than obtain the marked-up file. Optional sourcePassword / targetPassword. |
GetDocumentInfo |
Inspects 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 formats to expect. Optional password for protected documents. |
Example prompts for AI agents
Once the server is wired up to your MCP client (Claude Desktop, Cursor, VS Code Copilot, …), try:
Compare old.pdf and new.pdf and save the marked-up result.
Diff contract-v1.docx against contract-v2.docx and tell me the change count.
What changed between proposal-v1.docx and proposal-v2.docx? Summarize the edits.
Did the prices change between budget-q1.xlsx and budget-q2.xlsx? Which cells?
How many pages does report.pdf have? Who's the author?
Inspect /docs/legal-brief.pdf — what's the file type and page count?
The client picks Compare when the user wants the rendered diff file,
AnalyzeChanges when they only want to know what changed (summary /
analysis, no file), and GetDocumentInfo for inspection-only questions.
Licensing
The MCP server itself is MIT; the underlying GroupDocs.Comparison engine requires a license for production use. Without one the server runs in evaluation mode:
- Comparison output may carry evaluation watermarks / notices.
- A single server process can open at most 15 documents; further calls fail with an evaluation-cap error until the server restarts.
To lift the limits, point GROUPDOCS_LICENSE_PATH at your GroupDocs.Total.lic:
Configuration
| Variable | Description | Default |
|---|---|---|
GROUPDOCS_MCP_STORAGE_PATH |
Base folder for input and output files | current directory |
GROUPDOCS_MCP_OUTPUT_PATH |
(Optional) separate folder for output files | GROUPDOCS_MCP_STORAGE_PATH |
GROUPDOCS_LICENSE_PATH |
Path to GroupDocs license file | (evaluation mode) |
Usage with Claude Desktop
{
"mcpServers": {
"groupdocs-comparison": {
"type": "stdio",
"command": "dnx",
"args": ["GroupDocs.Comparison.Mcp", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "/path/to/documents"
}
}
}
}
To pin to a specific version, replace
"GroupDocs.Comparison.Mcp"with"GroupDocs.Comparison.Mcp@26.7.4"inargs. Pinning is recommended for shared / committed configs to avoid surprise upgrades.
Usage with VS Code / GitHub Copilot
NuGet.org generates a ready-to-use mcp.json snippet on the package page.
Copy it directly into your .vscode/mcp.json.
Alternatively, add manually to .vscode/mcp.json:
{
"inputs": [
{
"type": "promptString",
"id": "storage_path",
"description": "Base folder for input and output files.",
"password": false
}
],
"servers": {
"groupdocs-comparison": {
"type": "stdio",
"command": "dnx",
"args": ["GroupDocs.Comparison.Mcp", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "${input:storage_path}"
}
}
}
}
Same pinning rule as above — swap
"GroupDocs.Comparison.Mcp"for"GroupDocs.Comparison.Mcp@26.7.4"to lock to a specific release.
Usage with Docker Compose
cd docker
docker compose up
Edit docker/docker-compose.yml to point volumes at your local documents folder.
Documentation & guides
Step-by-step deployment guides and a published-package integration test suite live in the companion repo GroupDocs.Comparison.Mcp.Tests:
- Install from NuGet —
dnx, global tool, pinned vs always-latest - Run via Docker
- Verify on the MCP registry
- Use with Claude Desktop
- Use with VS Code / GitHub Copilot
- Run the integration tests
That repo also exercises every advertised tool against the published NuGet artifact on Linux, macOS, and Windows in CI — so the snippets above are verified end-to-end on every release.
License
MIT — see LICENSE
<!-- mcp-name: io.github.groupdocs-comparison/groupdocs-comparison-mcp -->
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。