MintPDF MCP Server

What the code does

We read the source, 3 d ago · tools taken from the live server · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  return new Function(`return (${src})`)();

import { readdirSync, readFileSync, existsSync } from "node:fs";

        paperEl.innerHTML = m.doc;

<script defer src="https://cloud.umami.is/script.js" data-website-id="7a43ccd2-b47d-45c2-bb22-05fc5fd46daa" data-domains="mintpdf.dev"></script>

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

claude mcp add mintpdf --transport http https://pdfmint-production-0b25.up.railway.app/mcp

https://pdfmint-production-0b25.up.railway.app/mcp

[mcp_servers.mintpdf]
url = "https://pdfmint-production-0b25.up.railway.app/mcp"

{
  "mcpServers": {
    "mintpdf": {
      "url": "https://pdfmint-production-0b25.up.railway.app/mcp"
    }
  }
}

{
  "servers": {
    "mintpdf": {
      "type": "http",
      "url": "https://pdfmint-production-0b25.up.railway.app/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints