GroupDocs.Redaction.Mcp

GroupDocs.Redaction MCP Server

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

Installation

Requires .NET 10 SDK.

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

dnx GroupDocs.Redaction.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 [email protected] --yes

Or install as a global dotnet tool:

dotnet tool install -g GroupDocs.Redaction.Mcp
groupdocs-redaction-mcp

Or run via Docker:

docker run --rm -i \
  -v $(pwd)/documents:/data \
  ghcr.io/groupdocs-redaction/redaction-net-mcp:latest

Native prerequisites

The underlying GroupDocs engine uses System.Drawing (GDI+) for image-area redaction (drawing solid-color boxes over page regions). When you run the server natively (via dnx or the global dotnet tool) on Linux or macOS, install the native libgdiplus library first:

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

Example prompts

• "Redact all occurrences of 'John Smith' in contract.docx"
• "Remove all metadata from report.pdf before sharing it externally"
• "Delete all comments and annotations from review.docx"
• "Cover the signature area on page 1 of agreement.pdf with a black box from (100,200) to (400,300)"
• "How many pages does confidential.pdf have?"

Configuration

Usage with Claude Desktop

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

To pin to a specific version, replace "GroupDocs.Redaction.Mcp" with "[email protected]" in args. 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-redaction": {
      "type": "stdio",
      "command": "dnx",
      "args": ["GroupDocs.Redaction.Mcp", "--yes"],
      "env": {
        "GROUPDOCS_MCP_STORAGE_PATH": "${input:storage_path}"
      }
    }
  }
}

Same pinning rule as above — swap "GroupDocs.Redaction.Mcp" for "[email protected]" 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.Redaction.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