MinerU MCP Server

If you already use MinerU, the mineru mcp server is the piece that lets your assistant work with it directly. MinerU document parsing API — PDFs, images, DOCX, PPTX with OCR and batch processing.

What the server does

MCP server for MinerU document parsing API — extract text, tables, and formulas from PDFs, DOCs, and images.

• VLM model — — 90%+ accuracy for complex documents
• Pipeline model — — Fast processing for simple documents
• Local file upload — — Upload files from disk for batch parsing
• Batch processing — — Parse up to 200 documents at once
• Download & rename — — Extract markdown with original filenames
• Page ranges — — Extract specific pages only

Installation

The server ships on npm as mineru-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• mineru_parse — Parse a document URL
• mineru_status — Check task progress, get download URL
• mineru_batch — Parse multiple URLs (max 200)
• mineru_batch_status — Get batch results with pagination
• mineru_upload_batch — Upload local files for batch parsing
• mineru_download_results — Download results as named markdown files
• Cursor — The Cursor tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• Cline — Open MCP Servers icon in Cline panel > Configure > Advanced MCP Settings, then add:
• Witsy — In Settings > MCP Servers, add a new server with Type: stdio, Command: npx, Args: -y mineru-mcp, and set environment variable MINERU_API_KEY to your
• Windows — On Windows, npx requires a shell wrapper. Replace "command": "npx" with:
• ChatGPT — ChatGPT only supports remote MCP servers over HTTPS — local stdio servers like this one are not directly supported. You would need to deploy behind a

Credentials and setup notes

Configuration is passed through the environment: MINERU_API_KEY, MINERU_BASE_URL. 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.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MinerU.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MinerU's toolset — mineru_parse, mineru_status, mineru_batch and 9 more — is a fair guide to whether it matches your workflow. It is maintained by linxule; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MinerU's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.