npm v0.4.0 · MIT · Node.js 20.9+

Your AI understands the task. Give it 97 PDF tools to finish it.

1PDF MCP gives Codex, Claude, Cursor and other Agents reliable PDF execution through natural language. Install once, then merge, convert, secure and analyze files without asking your Agent to improvise a script.

View on npm View source

Install for Codex

stdio

codex mcp add 1pdf -- npx -y onepdf-mcp-server

Then open Codex and ask: “Merge these contracts, remove blank pages and add page numbers.”

One server, broad coverage

From one-off edits to multi-step workflows

Agents handle intent and sequencing. 1PDF performs the file operations and returns structured, truthful results.

12 tools

Organize

Merge, split, reorder, rotate, extract and remove pages.

24 tools

Convert

Move between PDF, images, Office, Markdown, email and ebook formats.

15 tools

Edit & secure

Watermark, number, crop, encrypt, sanitize, sign and fill forms.

46 tools

Analyze & specialize

Read, compare, extract tables and images, rasterize and automate layouts.

Works with your MCP client

Codex

CLI, desktop app and IDE extension share the same MCP configuration.

Claude

One command for Claude Code, or a small JSON block for Claude Desktop.

Cursor

Add the npm command as a local stdio server in MCP settings.

Other MCP clients

Use any client that can launch a local stdio server with npx.

Public evidence kit · reviewed 2026-08-04

Reproduce two local agent workflows

These tasks use a harmless public two-page fixture, a pinned package version, explicit output paths, and bounded checks. Agent wording and intermediate files can vary; verify the final PDF instead of treating a chat response as proof.

Public input fixture

A generated two-page PDF containing fictional metadata and visible page markers. Make two copies for the merge task.

Download 1pdf-local-processing-sample.pdf

mkdir -p onepdf-mcp-check/output && cd onepdf-mcp-check && curl -L https://1pdf.best/private-pdf-tools-sample.pdf -o sample-a.pdf && cp sample-a.pdf sample-b.pdf

Codex

Pinned install

codex mcp add 1pdf -- npx -y onepdf-mcp-server@0.4.0

Copyable task

Use the 1PDF MCP server. Call system_status first. Rotate every page of ./sample-a.pdf 90 degrees clockwise and save the final PDF as ./output/codex-rotated.pdf. Do not overwrite the input. Report the output path and page count; do not claim success unless the file exists.

Expected file: ./output/codex-rotated.pdf

The input file still exists and remains unchanged.
The output opens as a two-page PDF.
Both visible page markers are rotated 90 degrees clockwise.

Boundary: This checks system_status plus one core rotate operation. It does not test optional converters, every Codex surface, arbitrary PDFs, or whether the Agent chose the shortest possible tool sequence.

Claude Code

Pinned install

claude mcp add 1pdf -- npx -y onepdf-mcp-server@0.4.0

Copyable task

Use the 1PDF MCP server. Merge ./sample-a.pdf followed by ./sample-b.pdf and save the final PDF as ./output/claude-merged.pdf. Do not overwrite either input. Report the output path and page count; do not claim success unless the file exists.

Expected file: ./output/claude-merged.pdf

Both input files still exist and remain unchanged.
The output opens as a four-page PDF.
The visible page markers appear in the order 1, 2, 1, 2.

Boundary: This checks one core merge operation in Claude Code. It does not test Claude Desktop, remote MCP transport, optional local programs, malformed inputs, or the semantic correctness of unrelated tools.

Compatibility boundaries

Run the setup command from a directory the Agent can access, then start the Agent in that directory so the relative paths resolve.
The pinned commands reproduce npm version 0.4.0. The unpinned quick-start commands elsewhere on this page intentionally resolve the current npm latest release.
Core tools execute through a local stdio server. Nine document-conversion tools and some specialized operations require optional local programs; call system_status before those workflows.
A created file, page count, and visible fixture markers are the checks. The Agent’s prose response alone is not evidence that processing succeeded.

Verification ledger

npm onepdf-mcp-server@0.4.0

npm package metadata records version 0.4.0, the MIT license, and Node.js 20.9 or newer.

Source revision 985ba0a

Immutable public source snapshot used to check the README, tool inventory, development commands, and capability boundaries.

Official MCP Registry query

The official MCP Registry API returned zero matching entries for “onepdf” on the checked date. This is a dated discovery check, not a permanent status claim.

Read the machine-readable workflow evidence →

Install

Add 1PDF to the Agent you already use

No account or API key is required for the core MCP tools.

Codex

Official setup docs

Run the command once in your terminal. The CLI, desktop app and IDE extension share the configuration.

codex mcp add 1pdf -- npx -y onepdf-mcp-server

Claude Code

Official setup docs

Add the local stdio server at project scope, then check it with “claude mcp list”.

claude mcp add 1pdf -- npx -y onepdf-mcp-server

Claude Desktop and Cursor

In Claude Desktop, add the configuration block to claude_desktop_config.json. In Cursor, open Settings → MCP → Add Server and use npx as the command with -y and onepdf-mcp-server as arguments.

{
  "mcpServers": {
    "1pdf": {
      "command": "npx",
      "args": ["-y", "onepdf-mcp-server"]
    }
  }
}

system_status

Know what is available before a workflow starts

Ask your Agent to call system_status before Office, ebook, DjVu, XPS, Ghostscript, or PDF/A work. It reports installed programs, enabled tools, and platform-specific setup instructions for anything missing.

$ Ask 1PDF to check its available capabilities

✓ Core PDF tools ready

→ Optional converters reported individually

Ready to use

Turn a PDF request into a completed file.

Install the free MCP server, attach your files to your Agent, and describe the result you want.

Install from npm Browse web tools