convert_fileLABSCO SUMMARY
Length caps on every conversion, which is what keeps a long PDF usable.
Each tool takes a maximum output length, and the directory tool takes a file limit too — so pointing it at a folder of long reports fails politely instead of consuming everything. Conversion happens in memory with no temporary files left behind.
What it is
A small document-conversion server. It reads files from disk or fetches a URL, converts the content to Markdown in memory, and caps the output length so a large document does not swamp the conversation.
What you get
- convert_file — one local file to Markdown, with a maximum output length you can set
- convert_url — fetch a URL and convert what comes back
- batch_convert — several files in one call, with a per-file length cap
- convert_directory — every supported file in a directory, optionally recursive, with a file limit
- extract_metadata — metadata from a file without converting the whole thing
- list_supported_formats — what it will accept
- Support for PDF, DOCX, HTML, EPUB, CSV, JSON, images via OCR and plain text
Requirements
Python, or the bundled Dockerfile. Install the requirements and run the module over stdio; with Docker, mount the directory holding the files you want to convert. No credentials.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Reading a PDF never meant for a model
Convert the file to Markdown with a length cap, and get structured text instead of a binary.
02
Pulling a page that resists a plain fetch
Fetch the URL and convert the content in the same call.
03
Ingesting a folder of documents
Convert everything supported in the directory, recursively if you want, up to a file limit you set.
04
Deciding whether a file is worth converting
Read its metadata first, and check the format is supported before committing to a full pass.
6 tools
Listed in project docs. Your client may show a different list.
convert_urlbatch_convertconvert_directoryextract_metadatalist_supported_formatsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
python on PATH
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
python -m mcp_server_convertMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"convert": {
"command": "python",
"args": [
"-m",
"mcp_server_convert"
],
"cwd": "<YOUR_PATH_TO_MCP_SERVER_CONVERT>"
}
}
}Claude Code — Docker
CLAUDE CODE — DOCKER · JSON
{
"mcpServers": {
"convert": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-v",
"<YOUR_PATH_TO_FILES>:/data",
"mcp-server-convert"
]
}
}
}
