Groupdocs Merger Mcp

io.github.groupdocs-merger由 GitHub 帳號 groupdocs-merger 發布v26.9.0更新於 Oct 24, 2026

MCP server for GroupDocs.Merger — merge, split, and inspect documents via AI agents.

已驗證STDIO僅桌面效率與工作流檔案與儲存

概覽

AI 產生的概覽

本機 MCP 伺服器,包裝 GroupDocs.Merger,讓助理合併、拆分與檢視 PDF、Office 等文件。

可以做什麼
  • 將 2–4 份文件合併成單一檔案並存到儲存目錄
  • 依指定頁面拆分文件,把每頁存成個別檔案
  • 以 JSON 回傳檔案類型、頁數、大小與每頁尺寸,且不改動原檔
  • 查詢目前授權模式,計量計費下還可查看已用量與剩餘額度
  • 支援 PDF、DOCX、XLSX、PPTX 及 30 多種文件、影像與壓縮檔格式
適用情境
適合讓助理在聊天用戶端內合併報告或附錄、從合約或手冊抽出指定頁面,或在處理前先確認文件頁數等情境。
執行需求
以 stdio 在本機執行;透過 dnx 或全域 dotnet 工具安裝需 .NET 10 SDK,也可改用 Docker。在 Linux/macOS 原生執行需先安裝 libgdiplus。需設定 GROUPDOCS_MCP_STORAGE_PATH(可選 GROUPDOCS_MCP_OUTPUT_PATH)指向文件資料夾。要解除評估限制需以 GROUPDOCS_LICENSE_PATH 提供授權檔,或設定計量金鑰組。
安裝前請注意
未授權時以評估模式執行:輸出可能帶浮水印,單一程序最多開啟 15 份文件,超過即失敗。計量模式依實際用量計費,並向 GroupDocs 伺服器回報用量,需要對外網路連線。GROUPDOCS_METERED_PRIVATE_KEY 是密鑰,應放在作業系統環境變數,不要寫進會提交的專案設定。合併與拆分會在設定的儲存資料夾寫入新檔案。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Groupdocs Merger Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

GroupDocs.Merger MCP Server

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

[NuGet] [NuGet downloads] [Docker pulls] [MCP Registry] [Integration tests] [License: MIT]

Installation

[Install in VS Code] [Install in VS Code Insiders] [Add to Cursor] [Codex CLI setup] [Windsurf setup]

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/.

Requires .NET 10 SDK.

Run directly with dnx (recommended — no install step):

bash
dnx GroupDocs.Merger.Mcp --yes

Pulls the latest stable release on every invocation. To pin to a specific version (recommended for shared configs and CI), append @<version>:

bash

Or install as a global dotnet tool:

bash
dotnet tool install -g GroupDocs.Merger.Mcpgroupdocs-merger-mcp

Or run via Docker:

bash
docker run --rm -i \  -v $(pwd)/documents:/data \  ghcr.io/groupdocs-merger/merger-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:

PlatformSetup
WindowsNothing — GDI+ is built into the OS.
Linuxsudo apt-get install -y libgdiplus libfontconfig1
macOSbrew install mono-libgdiplus
DockerNothing — 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

ToolDescription
MergeMerges 2–4 documents into a single file and saves the result to storage
SplitSplits a document by extracting specific pages, saving each as an individual file
GetDocumentInfoReturns the file type, page count, size, and per-page dimensions of a document as JSON (without modifying it)

All tools support PDF, DOCX, XLSX, PPTX, and 30+ more document, image, and archive formats.

Example prompts for AI agents

Copy any of these into Claude Desktop, Cursor, or GitHub Copilot Chat after the server is connected.

  1. Merge documents: "Merge intro.docx and appendix.docx into one file."
  2. Combine PDFs: "Combine report-q1.pdf, report-q2.pdf, and report-q3.pdf into a single PDF."
  3. Split out pages: "Split pages 3, 7, and 9 out of contract.pdf into separate files."
  4. Inspect before merging: "How many pages does presentation.pptx have?"
  5. Extract a page range: "Pull pages 1 through 5 of manual.docx into their own documents."

Licensing

The MCP server itself is MIT; the underlying GroupDocs.Merger engine requires a license for production use. Without one the server runs in evaluation mode:

  • Processed output may carry evaluation watermarks.
  • A single server process can open at most 15 documents; further calls fail with an evaluation-cap error until the server restarts.

There are two ways to license the server.

License file — point GROUPDOCS_LICENSE_PATH at your GroupDocs.Total.lic. Works offline.

Metered (pay-per-use) — set both GROUPDOCS_METERED_PUBLIC_KEY and GROUPDOCS_METERED_PRIVATE_KEY. You are billed for what you actually process, which suits AI agents well because their usage is bursty and hard to predict up front. If both a metered key pair and a license file are configured, metered wins and the file is ignored.

Metered mode needs outbound connectivity. Usage is reported to GroupDocs servers, so air-gapped or firewalled deployments must allow that egress — or use a license file instead.

Call the get_license_status tool at any time to see which mode is active, and — under metered — the consumed quantity and remaining credit.

Keeping the private key out of your config

The metered private key is a secret. MCP client configs are plain files on disk, and a project-scoped .mcp.json is committed by convention, so prefer, in order:

  1. Set the variables in your OS environment and leave them out of the config entirely. An stdio MCP server inherits its client's environment, so this works in every client. On macOS note that an app launched from Finder does not inherit shell exports — use launchctl setenv, or launch the client from a terminal.
  2. Reference them indirectly if your client supports it (Claude Code expands ${VAR}; VS Code uses ${env:VAR} and ${input:...}).
  3. A literal value in a user-scoped config (for example ~/.claude.json) is acceptable for a single developer.
  4. Never commit a literal key in a project-scoped .mcp.json.

For Docker, forward the values without writing them into any file:

bash
docker run --rm -i \  -e GROUPDOCS_METERED_PUBLIC_KEY -e GROUPDOCS_METERED_PRIVATE_KEY \  -v /path/to/documents:/data \  ghcr.io/groupdocs-merger/merger-net-mcp:latest

To lift the limits with a license file:

Configuration

VariableDescriptionDefault
GROUPDOCS_MCP_STORAGE_PATHBase folder for input and output filescurrent directory
GROUPDOCS_MCP_OUTPUT_PATH(Optional) separate folder for output filesGROUPDOCS_MCP_STORAGE_PATH
GROUPDOCS_LICENSE_PATHPath to GroupDocs license file. In evaluation mode, merged / split output may include watermarks(evaluation mode)
GROUPDOCS_METERED_PUBLIC_KEYMetered public key. Requires the private key too; takes precedence over the license file(unset)
GROUPDOCS_METERED_PRIVATE_KEYMetered private key. Secret - see Licensing(unset)

Usage with Claude Desktop

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

To pin: replace "GroupDocs.Merger.Mcp" with "[email protected]" in args.

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:

json
{  "inputs": [    {      "type": "promptString",      "id": "storage_path",      "description": "Base folder for input and output files.",      "password": false    }  ],  "servers": {    "groupdocs-merger": {      "type": "stdio",      "command": "dnx",      "args": ["GroupDocs.Merger.Mcp", "--yes"],      "env": {        "GROUPDOCS_MCP_STORAGE_PATH": "${input:storage_path}"      }    }  }}

Usage with Docker Compose

bash
cd dockerdocker 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.Merger.Mcp.Tests:

License

MIT — see LICENSE

來源:README.md,提交 6e1d4a4

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v26.9.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分