Install
No framework information available.
README
GroupDocs.Metadata MCP Server
MCP server that exposes GroupDocs.Metadata 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 [email protected] --yes
Or install as a global dotnet tool:
dotnet tool install -g GroupDocs.Metadata.Mcp
groupdocs-metadata-mcp
Or run via Docker:
docker run --rm -i \
-v $(pwd)/documents:/data \
ghcr.io/groupdocs-metadata/metadata-net-mcp:latest
Available MCP Tools
| Tool | Description |
|---|---|
ReadMetadata |
Reads all metadata properties (author, title, creation date, custom properties) and returns them as JSON |
RemoveMetadata |
Removes all metadata from a document and saves the cleaned file to storage |
Configuration
| Variable | Description | Default |
|---|---|---|
GROUPDOCS_MCP_STORAGE_PATH |
Base folder for input and output files | current directory |
GROUPDOCS_MCP_OUTPUT_PATH |
(Optional) separate folder for output files | GROUPDOCS_MCP_STORAGE_PATH |
GROUPDOCS_LICENSE_PATH |
Path to GroupDocs license file | (evaluation mode) |
Usage with Claude Desktop
{
"mcpServers": {
"groupdocs-metadata": {
"type": "stdio",
"command": "dnx",
"args": ["[email protected]", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "/path/to/documents"
}
}
}
}
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-metadata": {
"type": "stdio",
"command": "dnx",
"args": ["[email protected]", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "${input:storage_path}"
}
}
}
}
Usage with Docker Compose
cd docker
docker compose up
Edit docker/docker-compose.yml to point volumes at your local documents folder.
License
MIT — see LICENSE
Adoption Assessment
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.