MinerU MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

          const out = execFileSync("mdls", ["-raw", "-name", "kMDItemNumberOfPages", params.file], { timeout: 10_000 }).toString().trim();

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const result = spawnSync(process.execPath, [...workerLoaders,workerPath, JSON.stringify(command)], {

import { readFileSync, createWriteStream, readdirSync, statSync, mkdirSync, existsSync, unlinkSync, rmSync, realpathSync, copyFileSync } from "node:fs";

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mineru -- npx -y mineru-mcp

{
  "mcpServers": {
    "mineru": {
      "command": "npx",
      "args": [
        "-y",
        "mineru-mcp"
      ]
    }
  }
}

[mcp_servers.mineru]
command = "npx"
args = ["-y", "mineru-mcp"]

{
  "mcpServers": {
    "mineru": {
      "command": "npx",
      "args": [
        "-y",
        "mineru-mcp"
      ]
    }
  }
}

{
  "servers": {
    "mineru": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mineru-mcp"
      ]
    }
  }
}