MCP server for GroupDocs.Signature — sign, search and verify document signatures via AI agents.
Groupdocs MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for GroupDocs.Signature — sign, search and verify document signatures via AI agents.
MCP server that exposes GroupDocs.Signature as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents.
Once Groupdocs is connected, these are the calls the assistant has available:
Sign — Sign a document with a text, QR code, barcode, or digital certificate signature; saves the signed file as _signed.Verify — Verify signatures in a document (text, QR code, barcode, digital, or all) and return a validity reportSearchTextSignatures — Find embedded text signatures (stamps, labels, native text annotations) with optional substring filterSearchBarcodes — Find barcode signatures (Code39, Code128, EAN, etc.) with optional decoded-text filter and optional inline imageSearchQrCodes — Find QR code signatures with optional decoded-text filter and optional inline imageSearchDigitalSignatures — Find digital certificate signatures and return signer, issuer, serial number, validity statusSearchImageSignatures — Find embedded image signatures (logos, stamp images, picture overlays) and return them as base64 PNGsGetDocumentInfo — Return file type, page count, size, and per-page dimensions as JSON (no modification)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.
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.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Groupdocs's toolset — Sign, Verify, SearchTextSignatures and 5 more — is a fair guide to whether it matches your workflow. It is maintained by groupdocs-signature; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Groupdocs's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Sign | Sign a document with a text, QR code, barcode, or digital certificate signature; saves the signed file as <name>_signed.<ext> |
| Verify | Verify signatures in a document (text, QR code, barcode, digital, or all) and return a validity report |
| SearchTextSignatures | Find embedded text signatures (stamps, labels, native text annotations) with optional substring filter |
| SearchBarcodes | Find barcode signatures (Code39, Code128, EAN, etc.) with optional decoded-text filter and optional inline image |
| SearchQrCodes | Find QR code signatures with optional decoded-text filter and optional inline image |
| SearchDigitalSignatures | Find digital certificate signatures and return signer, issuer, serial number, validity status |
| SearchImageSignatures | Find embedded image signatures (logos, stamp images, picture overlays) and return them as base64 PNGs |
| GetDocumentInfo | Return file type, page count, size, and per-page dimensions as JSON (no modification) |
{
"mcpServers": {
"groupdocs-signature": {
"type": "stdio",
"command": "dnx",
"args": ["GroupDocs.Signature.Mcp", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "/path/to/documents"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GROUPDOCS_MCP_STORAGE_PATH | Filesystem location the server is allowed to use. | Optional |
| GROUPDOCS_LICENSE_PATH | Filesystem location the server is allowed to use. | Optional |
| GROUPDOCS_MCP_OUTPUT_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.