Groupdocs Merger MCP server
MCP server for GroupDocs.Merger — merge, split, and inspect documents via AI agents.
A90/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Groupdocs Merger yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Groupdocs Merger tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 15 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 90/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
The registry entry has no remote endpoint or installable package.
Groupdocs Merger: common questions
- Is Groupdocs Merger MCP server safe?
- Yes, by our scan: it is graded A (90/100). Read the Groupdocs Merger safety report
- Does Groupdocs Merger need an API key?
- No secret keys are declared. It reads 5 settings from the environment.
- Is Groupdocs Merger maintained?
- The last commit was 15 days ago (2026-09-05). The latest release is v26.9.0.