F
licenseNot graded
qualityD
maintenanceConverts documents (PDF, DOCX, images, etc.) to Markdown using Microsoft's Markitdown library, with no local setup required. Integrates with AI agents via MCP for seamless document conversion.
1
-
unfold-mcp
by Bytestay
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@unfold-mcpConvert this PDF to Markdown: https://example.com/report.pdf"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Unfold MCP server
Give your AI agent the content of PDF, Word (DOCX), PowerPoint (PPTX) and Excel (XLSX) documents as Markdown, from a URL or a local file.
The server is open source (MIT). It calls the Unfold API, which is paid, with a free plan.
You use your own key, from RapidAPI or api.market.
Every tool call is one request on your plan.
The free Basic plan has 15 requests a month, with a hard limit, so it never runs up a bill.
1. Get a key
Related MCP server: md-converter-mcp
2. Add the server to your MCP client
The server runs locally over stdio with uv. Put your key in its environment.
JSON configuration (Claude Desktop, Cursor, VS Code and most clients):
{
"mcpServers": {
"unfold": {
"command": "uvx",
"args": ["--from", "bytestay-unfold-mcp", "unfold-mcp"],
"env": { "RAPIDAPI_KEY": "your-rapidapi-key" }
}
}
}Claude Code:
claude mcp add unfold --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from bytestay-unfold-mcp unfold-mcpEnvironment
variable | meaning |
| your RapidAPI key |
| your api.market key, used when |
|
|
Without a key the server still starts. The first tool call then explains where to get one.
Also listed on Glama:
3. Tools
tool | what it does |
| converts one document to Markdown; give a public URL, or a local file to upload |
The format is detected from the content.
Every tool returns the API's JSON response.
When the marketplace reports it,
quota_remainingis added: the requests left on your plan this month.Errors are explained in plain words, with what to do next:
key refused, with the link to subscribe;
quota reached, with the plans;
input the API couldn't process, with the API's reason.
Privacy
Local files are read only when a tool is given their path. They are sent to the API for that one request.
The API processes inputs in memory and doesn't store them. See the privacy policy.
Your key is only sent to the marketplace you chose.
Limits
Local files up to 10 MB.
Markdown up to 500,000 characters.
The server needs Python 3.10+ (uv installs it for you).
Development
uv venv && uv pip install -e ".[dev]"
.venv/bin/pytest # unit tests, no network; 100% coverage required
.venv/bin/ruff check src tests scriptsscripts/e2e_stdio.py unfold runs the server over stdio, as a client would, and calls its tools against the real API. It needs RAPIDAPI_KEY or API_MARKET_KEY.
Licence
MIT. Unfold itself is a paid API with a free plan, run by ByteStay.
Available Tools
1 toolconvert_documentARead-onlyIdempotent
Convert one document to Markdown. Give either url or path. The format is detected from the content.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Public http(s) URL of the document. | |
| path | No | Local file to upload instead (up to 10 MB). | |
| max_chars | No | Cut the Markdown to this many characters. |
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavior ('format is detected from the content'), but omits notable traits: all three parameters are optional so neither url nor path is formally required, and nothing is said about truncation effects, failure modes, or unsupported inputs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core purpose and then the input and format rules. Nothing is padded and nothing repetitive.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (3 flat params, no nesting, no output schema), and the description covers the essentials of what it does and how to supply input. However, with no output schema it should say more about what is returned and that max_chars can truncate the result, and it never states what happens when both or neither of url/path is given.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not state: url and path are mutually exclusive alternatives ('either ... or'), and the input format is inferred rather than declared. That mutual-exclusivity note meaningfully constrains how the agent fills the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a concrete verb and resource ('Convert one document to Markdown') and names the output format, so an agent knows exactly what comes back. It does not enumerate which input formats are supported, which keeps it from being a fully specified 5, and there are no siblings to differentiate against.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Give either `url` or `path`' is a parameter rule rather than a when-to-use rule; usage is only implied by the conversion framing. There are no alternatives to route between and no stated exclusions or preconditions (e.g. unsupported formats, network access limits), so the guidance is adequate but thin.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.2.2- First observed
convert_document
TDQS
A3.8/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is nothing to confuse it with. Its purpose—converting a document to Markdown—is stated explicitly and unambiguously.
Naming Consistency5/5
A single name, `convert_document`, follows a clear verb_noun snake_case convention. There are no competing conventions to conflict with it.
Tool Count3/5
One tool matches the narrow stated purpose of document-to-Markdown conversion, but it is a thin surface with no room for batch conversion, listing, or format-specific variants. It is borderline thin rather than clearly over- or under-scoped.
Completeness4/5
The tool accepts either a URL or a path and auto-detects format, covering both common input sources for the core conversion operation. Minor gaps remain: no batch conversion, no output options or post-conversion actions, and no way to inspect or validate a source before converting.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Convert PDFs, Office files, spreadsheets and images to clean Markdown, sized for agent context.
Convert PDF, Word, Excel and scanned documents to Markdown, tables and RAG chunks. OCR.
Convert, create and edit Word, PowerPoint, Excel and PDF documents from any AI agent.
Any URL to clean markdown/JSON; PDF, XLSX, CSV, DOCX to text and tables. Free tier for agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceConverts files (PDF, DOCX, PPTX, XLSX, images via OCR) and URLs to Markdown, enabling AI clients to read them via a single MCP tool.1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect and convert PDF, PowerPoint, Excel, and many other file formats into clean, structured Markdown, with chunking support for long documents.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents and MCP-capable platforms to convert documents such as docx, pptx, xlsx, pdf, odt, rtf, epub, and csv into clean GitHub-Flavored Markdown through a single tool call. Runs fully locally with no API key, no network access, and no OCR, returning structured errors for scanned, encrypted, or unsupported files.112 npmMIT