
Groupdocs Markdown Mcp
- Updated July 25, 2026
- groupdocs-markdown/GroupDocs.Markdown.Mcp
GroupDocs Markdown MCP is a MCP server that converts documents to Markdown via AI agents.
About
GroupDocs Markdown MCP targets developers who live in Markdown—Docusaurus, VitePress, README-driven products—but still receive Word or PDF from clients, regulators, or legacy systems. The server exposes conversion to Markdown so your agent can produce repo-ready files under GROUPDOCS_MCP_OUTPUT_PATH without a separate desktop export macro. That accelerates build-docs work: migrating an old manual, splitting chapters for AI search, or prepping ingestion chunks for a support bot. Configuration mirrors other GroupDocs MCP servers, which lowers friction if you already run Comparison or Conversion. Complexity is intermediate because you must manage paths, licensing for heavy batches, and validate MD fidelity on tables and images. It is a focused integration rather than a full static-site generator; pair with your own lint and deploy steps after conversion.
- Convert documents to Markdown through dedicated GroupDocs.Markdown MCP tools
- stdio transport with NuGet package GroupDocs.Markdown.Mcp (v26.5.0)
- Same three GroupDocs MCP environment variables for storage, output, and license
- Agent-driven batch path from client deliverables into git-friendly MD
- Evaluation mode without license file per manifest
Groupdocs Markdown Mcp by the numbers
- Data as of Jul 26, 2026 (Skillselion catalog sync)
claude mcp add GroupdocsMarkdownMcp -- npx -y groupdocs-markdown/GroupDocs.Markdown.McpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Last updated | July 25, 2026 |
|---|---|
| Repository | groupdocs-markdown/GroupDocs.Markdown.Mcp ↗ |
What it does
Turn Word, PDF, and other sources into Markdown so agents can edit docs, seed RAG corpora, or open PRs on your docs repo.
Who is it for?
Best when you're migrating help centers, policies, or course material into MD-based sites and agent workflows.
Skip if: Teams already authoring solely in Markdown or needing rich WYSIWYG editing instead of conversion.
What you get
Source files become Markdown artifacts in your output folder ready for commit, review, or RAG indexing.
- Markdown files in configured output directory
- Agent-usable conversion logs and paths for follow-up edits
- Reduced manual copy-paste from legacy doc formats
By the numbers
- Server version 26.5.0
- stdio MCP transport
- NuGet identifier GroupDocs.Markdown.Mcp
README.md
GroupDocs.Markdown MCP Server
MCP server that exposes GroupDocs.Markdown as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents — convert documents to clean, structured Markdown.
Installation
Requires .NET 10 SDK.
Run directly with dnx (recommended — no install step):
dnx GroupDocs.Markdown.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 GroupDocs.Markdown.Mcp@26.5.0 --yes
Or install as a global dotnet tool:
dotnet tool install -g GroupDocs.Markdown.Mcp
groupdocs-markdown-mcp
Or run via Docker:
docker run --rm -i \
-v $(pwd)/documents:/data \
ghcr.io/groupdocs-markdown/markdown-net-mcp:latest
No native prerequisites are required on any platform — the underlying
GroupDocs.Markdown engine renders image-bearing documents through a
self-contained SkiaSharp native asset, so dnx, the global tool, and the
Docker image all run with no extra apt/brew setup.
Available MCP Tools
| Tool | Description |
|---|---|
ConvertToMarkdown |
Converts a document (PDF, DOCX, XLSX, EPUB, MOBI, …) to clean, structured Markdown and saves the .md to storage. Images embed as base64 by default. |
GetDocumentInfo |
Returns file format, page count, title, author, and encryption flag as JSON, without converting. |
Reverse Markdown → document composition is not yet implemented in the underlying GroupDocs.Markdown 26.3.0 engine (
MarkdownConverter.FromMarkdownStringthrowsNotImplementedException), so this server does not expose aComposeFromMarkdowntool. Use the GroupDocs.Conversion MCP with a.mdsource file if you need Markdown → DOCX / PDF / HTML output today.
Example prompts for AI agents
- "Convert report.pdf to Markdown"
- "Export business-plan.docx as Markdown with images embedded as base64"
- "Convert pages 1-3 of contract.pdf to Markdown, text only — skip images"
- "How many pages does business-plan.pdf have?"
- "What format and author does cost-analysis.xlsx have?"
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) |
In evaluation mode (no license) the converted Markdown may be limited and can
include an evaluation notice. Supply GROUPDOCS_LICENSE_PATH for unrestricted
output.
Usage with Claude Desktop
{
"mcpServers": {
"groupdocs-markdown": {
"type": "stdio",
"command": "dnx",
"args": ["GroupDocs.Markdown.Mcp", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "/path/to/documents"
}
}
}
}
To pin to a specific version, replace
"GroupDocs.Markdown.Mcp"with"GroupDocs.Markdown.Mcp@26.5.0"inargs. 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-markdown": {
"type": "stdio",
"command": "dnx",
"args": ["GroupDocs.Markdown.Mcp", "--yes"],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "${input:storage_path}"
}
}
}
}
Same pinning rule as above — swap
"GroupDocs.Markdown.Mcp"for"GroupDocs.Markdown.Mcp@26.5.0"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.Markdown.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
Recommended MCP Servers
How it compares
Document-to-Markdown MCP bridge, not a static site generator or SEO skill.
FAQ
Who is GroupDocs Markdown MCP for?
Developers who use Markdown for docs or AI context and need automated conversion from Office or PDF sources.
When should I use GroupDocs Markdown MCP?
Use it while building documentation when you receive non-Markdown files and want the agent to emit.md under your storage paths.
How do I add GroupDocs Markdown MCP to my agent?
Install GroupDocs.Markdown.Mcp via NuGet stdio config, set GROUPDOCS_MCP_STORAGE_PATH and optional output/license env vars, then enable in MCP settings.