MCP server for GroupDocs.Metadata — read and remove document metadata via AI agents.
Connect Groupdocs to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for GroupDocs.Metadata — read and remove document metadata via AI agents. The groupdocs mcp server is what makes that connection.
MCP server that exposes GroupDocs.Metadata as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
ReadMetadata — Reads all metadata properties (author, title, creation date, custom properties) and returns them as JSONSearchMetadata — Searches within one document and returns only matching properties (filter by category, name, or value) — e.g. "show me the author", "does this haveWriteMetadata — Sets, changes, or adds a property (Author, Title, Subject, Keywords, Comments, Copyright, Company, Manager) and saves the updated fileRemoveMetadata — Removes metadata and saves a cleaned file. Strips everything by default, or only specific categories (gps, author, comments, company, datesGetDocumentInfo — Returns the file type, MIME type, page count, byte size, and encryption status as JSON — a lightweight structural check that does not enumerateConfiguration is passed through the environment: GROUPDOCS_MCP_STORAGE_PATH, GROUPDOCS_LICENSE_PATH, GROUPDOCS_MCP_OUTPUT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
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.
Plenty of developer tooling 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 — ReadMetadata, SearchMetadata, WriteMetadata and 2 more — is a fair guide to whether it matches your workflow. It is maintained by groupdocs-metadata; 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.
| Tool | What it does |
|---|---|
| ReadMetadata | Reads all metadata properties (author, title, creation date, custom properties) and returns them as JSON |
| SearchMetadata | Searches within one document and returns only matching properties (filter by category, name, or value) — e.g. "show me the author", "does this have GPS?" |
| WriteMetadata | Sets, changes, or adds a property (Author, Title, Subject, Keywords, Comments, Copyright, Company, Manager) and saves the updated file |
| RemoveMetadata | Removes metadata and saves a cleaned file. Strips everything by default, or only specific categories (gps, author, comments, company, dates, software, copyright, keywords, personal) |
| GetDocumentInfo | Returns the file type, MIME type, page count, byte size, and encryption status as JSON — a lightweight structural check that does not enumerate metadata properties |
{
"mcpServers": {
"groupdocs-metadata": {
"type": "stdio",
"command": "dnx",
"args": ["GroupDocs.Metadata.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.