Home · Setup · VS Code

MCP PDF Tools in VS Code

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.

In agent mode pdf_merge and pdf_stamp are tools the agent can reach mid-task, so "stamp this PAID, then attach it to the release notes" is one instruction instead of a manual export step.

What you get in VS Code

You say	Tool
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 VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

Scope	Path
This workspace	`<workspace>/.vscode/mcp.json`
Every workspace	`the user profile mcp.json, opened by the MCP: Open User Configuration command`

If you also run Claude Desktop, the shortest path there is one click: pdf.mcpb from the bundle catalog opens as an extension, with no JSON and no terminal. VS Code reads its own config, so here it is:

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "pdf": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/pdf/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"pdf","command":"node","args":["/absolute/path/to/mcp-servers/servers/pdf/dist/index.js"]}'

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/pdf

That writes servers/pdf/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

code --add-mcp '{"name":"pdf","command":"npx","args":["-y","@theluckystrike/mcp-pdf"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/pdf over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

{
  "servers": {
    "pdf": {
      "url": "https://mcp.zovo.one/mcp/pdf",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

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

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP PDF Tools tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

MCP PDF Tools in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro

Related guides & tools

Merge, split and stamp PDFs from chat, and why some come back as glyph numbers · Price drop alerts and PDF cleanup from chat: two small jobs you keep postponing · Splitting one big scan into separate documents · Merging a folder of receipts into one PDF from chat