Home · Setup · Cline

MCP PDF Tools in Cline

Merge, split, stamp and read PDFs, pure JavaScript, no upload. It merges and splits PDFs, extracts and reorders pages, rotates a sideways scan, stamps PAID or DRAFT or any text, watermarks the business name and VAT id from the shared profile, and reads text back best effort with no OCR.

pdf_info, pdf_count and pdf_text are safe to auto-approve since none of them write a file; leave pdf_merge, pdf_split, pdf_stamp and the rest behind a click, since each one creates a new file on disk.

What you get in Cline

You sayTool
Stamp PAID on this invoice and save a copy.pdf_stamp
Join these three PDFs into one file.pdf_merge
Split the scan: pages 1-3 are the invoice, 4 onwards is the receipt.pdf_split

The worked run stamped PAID on a 1-page invoice and wrote a new 0.9 MB file; the original file was byte-for-byte unchanged, which every writing tool here guarantees on purpose.

Install it in Cline

The file is mcp.json, and the key inside it is mcpServers.

ScopePath
Cline CLI~/.cline/mcp.json
The editor extensionopened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension
{
  "mcpServers": {
    "pdf": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-pdf"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

The npm publish of @theluckystrike/mcp-pdf is pending; until then use the .mcpb bundle or a clone and build from the latest release.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP PDF Tools runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

Free: info, count and text unlimited; merge up to 5 files; edits on files up to 30 pages; the PAID and DRAFT stamp presets. Pro is $19 once, verified offline.

Questions

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in. It is the one default here that sends you debugging a server that works.

Should I auto-approve MCP PDF Tools's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

Related

MCP PDF Tools in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs