Groupdocs MCP Server

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

Local serverstdio

What is the Groupdocs MCP server?

Groupdocs MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for GroupDocs.Merger — merge, split, and inspect documents via AI agents.

What you get

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

Setting it up

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.

What the assistant can call

Once Groupdocs is connected, these are the calls the assistant has available:

  • Merge — Merges 2–4 documents into a single file and saves the result to storage
  • Split — Splits a document by extracting specific pages, saving each as an individual file
  • GetDocumentInfo — Returns the file type, page count, size, and per-page dimensions of a document as JSON (without modifying it)

Configuration and credentials

You will need 3 environment variables: GROUPDOCS_MCP_STORAGE_PATH, GROUPDOCS_LICENSE_PATH, GROUPDOCS_MCP_OUTPUT_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the groupdocs mcp server does with a few real requests.

Choosing this one

Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Groupdocs's toolset — Merge, Split, GetDocumentInfo — is a fair guide to whether it matches your workflow. It is maintained by groupdocs-merger; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
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)

How to install the Groupdocs MCP server

{
  "mcpServers": {
    "groupdocs-merger": {
      "type": "stdio",
      "command": "dnx",
      "args": ["GroupDocs.Merger.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 Merge.
  • Use Groupdocs to Split.
  • Use Groupdocs to GetDocumentInfo.

Frequently asked questions

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